Explainer: https://github.com/bryanmcquade/scroll-to-css-selector
 

What are the primary use cases for this feature?  For reference, a primary use case is the core functionality of the feature (e.g. in GMail, a primary use case would be writing and sending an email).



What are the secondary use cases for this feature?  A secondary use case is still important, but something not done every day (e.g. in GMail, setting up email forwarding).



If launching for desktop platforms, can you completely interact with your UI and use your feature using only the keyboard? Is it always visually clear which item has focus?



If launching for desktop platforms, are any nonstandard keys required to interact with your UI using the keyboard, i.e. any keys other than Tab, Space, Enter, and arrow keys?



If launching for mobile platforms, are any custom/non-standard gestures required to interact with your feature, i.e. any any gestures aside from regular tapping, long pressing, or scrolling?



If your feature has any web component to it, does it pass an Accessibility Developer Tools Audit?  If not, please list any warnings / errors that appear.



Are you using color, sound, or an image/graphic as the primary way to communicate any information? If so, what alternative have you provided for users who have trouble seeing or hearing?



Does all text in the UI exceed a minimum of 4.5:1 contrast ratio?



Do buttons and images have proper labels?
 

At a high level, what metrics will you use to measure success?  How do they look in beta?



At a high level, what metrics will you use to detect regressions?  How do they look in beta?



If launching via Finch: are there any regressions in Heartbeat or Snapshot metrics?
 

if experiment  roll out was done:

=================================

- How did success metrics look during your stable experiment?



- How did regression metrics look during your stable experiment?



- If launching via Finch, are there any regressions in Heartbeat or Snapshot metrics?





if default roll out: 

====================

- At a high level, what metrics will you use to measure success? How do they look in dev/beta?



- At a high level, what metrics will you use to detect regressions? How do they look in dev/beta?

<b></b>
 

Please complete the Privacy Review before requesting legal review.   



If you've finished the Privacy Review, the legal reviewer will read your responses to the privacy survey to determine whether any of the privacy impacts are legally relevant.  For example, new data collection, new uses of existing data, or changes to strings on privacy-relevant settings.  How do users consent to that collection? 



Is your feature covered in the Chrome Privacy Notice (https:// www.google.com/chrome/privacy/  )   and if so, does the description of the feature need to be updated? 



Does your feature change the expectations or capabilities of third parties?  Example include the autoplay video policy launch which affected the rate at which video ads play by default or Data Saver which proxies browsing activity through an encrypted connection to a Google server thereby interfering with monitoring or URL blocking that might be done by network administrators. 



Does your feature involve using a Google server to manipulate or make a copy of third party content?  Examples include Data Saver, which fetches websites using a Google proxy.
 

!!! IMPORTANT !!!



When you flip the privacy review status to ReviewRequested, a separate privacy review bug will be automatically created for you (usually within 2 hours).



Please follow the instructions in that bug and continue the discussion there.



Do NOT use the comment thread below to avoid splitting the discussion. We are working on deprecating the privacy review bugs and migrating them to this comment thread, but this is not yet ready.



Please ping msramek@ if you have any questions about the process. Happy launching!



!!! IMPORTANT !!!
 

The security launch process is described at https:// chromium.googlesource.com/chromiumos/docs/+/master/security_review_howto.md  . 



Please ensure a design doc is attached with a completed "Security Considerations" section, instructions on what to cover are documented in security review HOWTO doc linked above. Once you're ready to start security review, set the status to ReviewRequested and we'll pick up the review.
 

Does the feature need manual testing?



Is the feature currently working, and is all code landed in canary and ready for testing?  Any currently known issues?



Are there flags or setup are needed to enable this feature?



Are there any special points of interest from a testing perspective?



Is the feature the same across all platforms?



What's automated (Unit tests, Integration tests, API tests, Browser tests, E2E tests)? Please provide links to automated tests.



What’s not automated that needs manual testing?
 

Please provide a link to your UX implementation review here before requesting review.