Issue metadata
Sign in to add a comment
|
Apps on the lockscreen should be able to work with screen off |
||||||||||||||||||||||||||||||||||||||
Issue descriptionFeature description: Bug 701078 adds the ability to have apps working on the lock screen. There's a strong desire to make these able to work with the screen off to enable note-taking use cases. The security questions around doing this are serious enough that this warrants its own launch bug. Eng owner: rkc Product owner: zalcorn Design doc (send to chrome-design-docs@): https://docs.google.com/document/d/1wPobf5WfDF6AgfNC--0eztGbl9VDmpy_XseuUZW-p4s/edit ################################################################# # Fill these surveys out as you are ready for various reviews. # ################################################################# Accessibility survey: The accessibility survey is included in a review bug that will be filed by lpalmaro@. Please answer all questions there. Legal survey: Email ctanaka@ (for non-Chrome OS) or jlchen@ (for Chrome OS) to request a legal review. Privacy survey: When you flip Launch-Status to Review-Requested, the privacy team will be notified. Once they've triaged your launch, a blocking privacy review bug will be filed. Fill out the privacy survey included in that bug. Email yitingc@ for any questions. Test survey (https://goto.google.com/chrome-test-questions): UI survey: Email chrome-ui-review@ (for non-Chrome OS) or chromeos-ui- review@ (for Chrome OS) to request a UI review if your launch will change any user-visible strings, assets, animations, or workflows.
,
Mar 15 2017
,
Mar 22 2017
Should we close this out bc it is Pbody only?
,
Mar 23 2017
We still see value in a product that allows screen-off note taking. I think it would be safe to de-prioritize this particular bug (as we no longer have the deadline pressure we did previously), but the suspending of the Pbody project does not imply that Lenovo are no longer interested in Halo keyboard devices or in the specific use cases we planning on addressing with that platform.
,
Mar 24 2017
+tbuckley Sounds good. I'm going to mark this milestone 63 for now, we can revisit at that time.
,
May 14 2017
,
Oct 30 2017
Removing a milestone until there is a clear need for this.
,
Feb 12 2018
This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 14 2018
This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 15 2018
We've added two new bits to the Launch template - Launch-Exp-Leadership and Launch-Leadership - to capture leadership approval for new features. The Launch-Exp-Leadership bit is meant to capture approval for Finch-based experimentation in the stable channel. However, since Chrome OS tends not to use Finch to experiment in the stable channel, setting this bit to NA for all Chrome OS-only launches. Ping amineer@ with any questions / concerns.
,
May 16 2018
Per updates to go/newChromeFeature, setting new Launch-Leadership bit (meant to capture leadership approval) to NotReviewed. Ping amineer@ for questions.
,
Jun 18 2018
,
Jul 11
[Bulk edit]: converting my launch bugs without target milestones to Feature Requests for better organizational sanity. They will retain Restrict-View-Google. Please ping me with any issues.
,
Nov 21
|
|||||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||||
Comment 1 by abodenha@chromium.org
, Mar 13 2017Cc: r...@chromium.org nathanb@lenovo-chrome.com jdufault@chromium.org tbarzic@chromium.org