New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 718772 link

Starred by 2 users
Status: WontFix
Owner:
steve...@chromium.org
Closed: Oct 2017
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Unnecessary bold font is seen for 'CHANGE CHANNEL' text in chrome://md-settings/help/details page.

Project Member Reported by jbanavatu@chromium.org, May 5 2017 
Chrome Version: 60.0.3086.3 / 9517.1.0 Daisy,Candy,Minnie
OS: Chrome OS

What steps will reproduce the problem?
(1)Sign in to chrome >> Navigate to chrome://md-settings/help/details page.
(2)Click on 'CHANGE CHANNEL' button >> Now click cancel and Observe 'CHANGE CHANNEL' text font

Expected: No such bold font should be seen for 'CHANGE CHANNEL' text in chrome://md-settings/help/details page.
Actual: Instead ,Unnecessary bold font is seen.

This is regression issue as no such bold font is seen in 58.0.3029.89/9334.58.0 stable channel Candy.

Attaching screen-cast for reference.
Actual.webm
1.3 MB View Download
Expected.webm
497 KB View Download

Comment 1 by steve...@chromium.org, May 8 2017

Cc: dpa...@chromium.org
Labels: -Pri-1 MD-Settings-AboutCrOS Pri-2
Definitely not a P1.

Looks like we just need to add the "secondary-class" button to get the settings focus behavior instead of the default paper-button focus behavior.

Comment 2 by dpa...@chromium.org, May 8 2017

Labels: -MD-Settings-AboutCrOS Hotlist-MD-Settings-AboutCrOS

Comment 3 by steve...@chromium.org, May 17 2017

Labels: -M-60 M-61

Comment 4 by steve...@chromium.org, Jun 26 2017

Labels: -M-61 M-62

Comment 5 by steve...@chromium.org, Aug 29 2017

Labels: -M-62 M-63

Comment 6 by steve...@chromium.org, Oct 5 2017

Status: WontFix (was: Assigned)
There were some changes to how primary/secondary buttons were marked and 'secondary' is now the default, which may have fixed it. This is currently WAI.
►

Sign in to add a comment