New issue
Advanced search Search tips

Issue 682975 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature
Launch-Accessibility: NeedInfo
Launch-Exp-Leadership: NA
Launch-Leadership: NotReviewed
Launch-Legal: NotReviewed
Launch-Privacy: NotReviewed
Launch-Security: NotReviewed
Launch-Test: NotReviewed
Launch-UI: NotReviewed

Blocked on:
issue 660170
issue 688024



Sign in to add a comment

Safe Mode

Project Member Reported by zalcorn@chromium.org, Jan 20 2017

Issue description

Feature description:
Allow users to boot into a "safe mode" that disables apps and extensions and sets settings and flags to default.

Eng owner: zalcorn
Product owner: wzang

#################################################################
# 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.

 

Comment 1 by st...@chromium.org, Jan 20 2017

Labels: -TL-rkc TL-steel

Comment 2 by wzang@chromium.org, Jan 20 2017

Cc: xiy...@chromium.org
Labels: -Launch-M-Target-58-Dev -Launch-M-Target-58-Beta -Launch-M-Target-58-Stable
Blockedon: 688024
Labels: Pri-3

Comment 6 by st...@chromium.org, Mar 3 2017

Cc: r...@chromium.org

Comment 7 by st...@chromium.org, Mar 3 2017

Cc: -st...@chromium.org
Labels: M-60
Labels: -M-60 M-64
Cc: abodenha@chromium.org
Labels: -TL-steel -M-64 TL-rkc M-66 Launch-M-Target-66-Dev Launch-M-Target-66-Beta Launch-M-Target-66-Stable
We should take a look at this again now that we're on the other side of Eve.
Labels: -M-66 -Launch-M-Target-66-Dev -Launch-M-Target-66-Beta -Launch-M-Target-66-Stable
Project Member

Comment 12 by sheriffbot@chromium.org, Feb 19 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

Comment 13 by amin...@google.com, May 15 2018

Labels: Launch-Exp-Leadership-NA
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.

Comment 14 by amin...@google.com, May 16 2018

Labels: Launch-Leadership-NotReviewed
Per updates to go/newChromeFeature, setting new Launch-Leadership bit (meant to capture leadership approval) to NotReviewed.  Ping amineer@ for questions.
Labels: -Launch-Accessibility-NotReviewed a11y-filed Launch-Accessibility-NeedInfo
Labels: Type-Feature
[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.
Components: UI>Shell>OOBE
Owner: jessejames@chromium.org
[bulk edit] moving OOBE/Login Feature Requests to Jesse.

Sign in to add a comment