New issue
Advanced search Search tips

Issue 670218 link

Starred by 1 user
Status: WontFix
Owner:
mustaq@chromium.org
Closed: Dec 2016
Cc:
ajha@chromium.org
gov...@chromium.org
pbomm...@chromium.org
mmoss@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Express.com dropdown menu items are too far left

Project Member Reported by pdr@chromium.org, Dec 1 2016 
Chrome Version: 56.0.2924.10
OS: MacOS

What steps will reproduce the problem?
(1) Go to Express.com
(2) Hover "men"
(3) Hover "shirts"

What is the expected result?
The shirt options ("Graphic Tees", "Hoodies & Sweatshirts", etc) are centered.

What happens instead?
The shirt options ("Graphic Tees", "Hoodies & Sweatshirts", etc) are too far left. If you mouse down on "shirts", the menu items are correctly centered.

This works in Firefox and Safari so I think we may have regressed. Requesting a bisect.
expressmenus.png
375 KB View Download

Comment 1 by ajha@chromium.org, Dec 1 2016

Cc: pbomm...@chromium.org gov...@chromium.org ajha@chromium.org
Components: Blink
Labels: -Pri-3 -Needs-Bisect M-55 hasbisect-per-revision ReleaseBlock-Stable OS-Linux OS-Mac OS-Windows Pri-1
Owner: mustaq@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on the latest canary(57.0.2938.0) and the latest beta(55.0.2883.59) of Windows-10, Mac OS 10.11.6 and Linux Ubuntu 14.04.

This is a regression issue broken in M-55.

Last good build: 55.0.2875.0 
First bad build: 55.0.2876.0

Changelog: https://chromium.googlesource.com/chromium/src/+log/bd027238e7f3d3c8096c1a62e9063d8cbf5d8a80..902a3d6303dfbfd49a24173777afcb4b70234a17

mustaq@: Could you please take a look at this. 

Note: Though this looks webpage specific as of now but visually looks really bad. Marking this as Stable blocker for M-55 and consideration for stable promotion or refresh thereafter. Please review the blocker label if this should not be blocking.

Comment 2 by ajha@chromium.org, Dec 1 2016 

Disabling the #pointer-events flag under chrome://flags resolves the issue.

Comment 3 by gov...@chromium.org, Dec 1 2016

Cc: mmoss@chromium.org

Comment 4 by mustaq@chromium.org, Dec 1 2016

Labels: Hotlist-Input-Dev
Status: Started (was: Assigned)

Comment 5 by mustaq@chromium.org, Dec 1 2016 

Looks like a site bug, shows the same problem in Edge.

Comment 6 by ajha@chromium.org, Dec 1 2016 

Just to update, works fine on Firefox and Safari as tested on Mac OS 10.11.6.

Comment 7 by mustaq@chromium.org, Dec 1 2016 

I meant that it's a site bug in PointerEvent specific code path.

Edge supports PointerEvent, Safari doesn't. FF support is off by default, turning it on (through "dom.w3c_pointer_events.enabled" in about:config) exposes the bug.

Comment 8 by mustaq@chromium.org, Dec 1 2016

Status: WontFix (was: Started)
Since it's a site bug that is exposed on other major browsers with PointerEvent support, I am marking it as WAI. The UX impact is minimal anyways.

- I originally suspected a coordinate issues in PointerEvent vs MouseEvent but found all coordinates matching between ME & PE.
- I will dig into the code to see if the bug is in some popular library.

Comment 9 by mustaq@chromium.org, Dec 1 2016

Labels: -ReleaseBlock-Stable PointerEvent
►

Sign in to add a comment