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

Issue 829792 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression: Border outline for NTP is not seen on dragging the blur slider in 'Add box-shadow' dialog.

Reported by dchau...@etouch.net, Apr 6 2018

Issue description

Chrome Version: 67.0.3390.0 (Official Build)Revision ae47769a6d274cb8eeca0f8e7b9198d0b043975f-refs/heads/master@{#548636} 32/64-bit.
OS: Win(7,8,8.1,10), Mac(10.12.6, 10.13.1, 10.13.4) and Linux (14.04 LTS).

What steps will reproduce the problem?
1. Launch Chrome, go to NTP, open DevTools window and go to 'Style' section,.
2. Hover the mouse pointer on three dot icon and select 'Add box-shadow' icon .
3. Now drag the Blur slider to it’s extreme right (20px) and observe the NTP

Actual: Border outline for NTP is not seen on dragging the blur slider in 'Add box-shadow' dialog.
Expected: Border outline for NTP should seen on dragging the blur slider in 'Add box-shadow' dialog.

This is a regression issue, broken in M-65 series, below is manual regression range.

Good build: 65.0.3287.0 (Revision: 522297)
Bad build: 65.0.3288.0 (Revision: 522666)

Using the per-revision bisect providing the bisect results:

You are probably looking for a change made after 522427 (known good), but no later than 522428 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/034134229bfcfe39482304614c615b826979d822..773623d293ed991e20596c4cb00e58610af5f395

Suspecting: https://chromium.googlesource.com/chromium/src/+/773623d293ed991e20596c4cb00e58610af5f395

@treib: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

NOTE: This issue is also reproducible on M-65 Stable (build # 65.0.3325.181) and M-66 Beta (build # 66.0.3359.81) and M-67 Dev (build # 67.0.3386.1)

Kindly review the attached screen-cast for reference.

Thank you.

 
Actual_behavior.mov
5.2 MB View Download
Expected behavior.mov
3.1 MB View Download
ContextData.xml
213 bytes View Download
wallpaper.xml
194 bytes View Download
Labels: zine-triaged

Comment 3 by treib@chromium.org, Apr 11 2018

Labels: -Pri-1 Pri-3
Owner: kristip...@chromium.org
The layout of the page (specifically the styling of the <body> element) changed at some point, which I guess had this side effect. You'd now have to apply the box-shadow to a different HTML element to see it.
Over to new NTP owners for consideration, but I think this is WontFix. It's certainly not P1.

Comment 4 by ramyan@chromium.org, Apr 11 2018

Cc: ramyan@chromium.org
Status: WontFix (was: Assigned)
Reverting recent styling changes to the body element doesn't affect the issue at all, so they're likely not the cause. The shadow should be outset anyway and not seen, so initial behavior seems like a bug and current behavior should be correct. I also agree that this is WontFix and is intended behavior.

Sign in to add a comment