DevRel-SAP: Button is partially highlighted
Reported by
orit.ha...@sap.com,
May 23 2017
|
|||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Open: Fiddle with SAPUI5: https://jsfiddle.net/95Loosr0/1/ Fiddle with only static html & css (no SAPUI5): https://jsfiddle.net/jm407pfo/1/ 2. Click on the “Test” button 3. Click outside the “Test” button 4. Hover over the “Test” button or click on and around the button What is the expected behavior? At step 2 the button should be fully highlighted At step 3 the button shouldn't be highlighted at all At step 4 the button should be fully highlighted when hovering the button and not highlighted when hovering outside the button. What went wrong? There is an inconsistent behavior in both Fiddles: At step 2: when clicking the button sometimes it is highlighted partially. At step 3: when clicking outside the button area, sometimes the button itself is highlighted partially. At step 4: when hovering the button it is partially highlighted. Did this work before? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 25.0 r0 The issue is reproducible also with version 59.0.3071.61 beta (64-bit) and version 60.0.3101.0 (Official Build) canary (64-bit). The issue occurs when the button is: - Within a scrollable container that currently shows a scrollbar - The scrollable container has a css property “flex-direction: column” (no problem if this property is disabled) - RTL is enabled
,
May 24 2017
Setting component to Blink>CSS since css flex-direction causes issues, per OP comments.
,
May 24 2017
Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac 10.12.4 with chrome Stable #58.0.3029.110, Canary #60.0.3108.0 Issue Broken in M54 Bisect Info: ============ Good Build : 54.0.2797.0, Revision Range- 405656 Bad Build : 54.0.2798.0, Revision Range- 405893 After executing the per-revision-bisect script, i got the following CL's between good and bad build versions ============================================ https://chromium.googlesource.com/chromium/src/+log/d588f3ad9391c547c7fb76eecb9cea84cab03846..799bc86d81b9a6efb6aac2ce1bbbe32a907bccb8 The suspecting CL : =================== https://chromium.googlesource.com/chromium/src/+/799bc86d81b9a6efb6aac2ce1bbbe32a907bccb8 Review-Url: https://codereview.chromium.org/2144413002 chrishtr@- Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner. Thank You...
,
May 24 2017
Chris, can we have a fix before M60 hits Stable?
,
May 24 2017
,
Jun 9 2017
Re comment 4: maybe. What is the urgency for fixing it now? It apparently broke in M54.
,
Jul 12 2017
Dropping priority if it's that old a regression :/
,
Jul 19 2017
,
Jul 21 2017
,
Oct 18 2017
,
Nov 30 2017
,
Dec 6 2017
,
Dec 6
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 10
,
Dec 10
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by ligim...@chromium.org
, May 23 2017Components: Blink
Labels: Needs-Bisect Needs-Triage-M58