Issue metadata
Sign in to add a comment
|
Incorrect behavior of "cursor: auto" over links
Reported by
friv...@gmail.com,
Jun 28 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: Open either of the following CSSWG tests: https://test.csswg.org/harness/test/css-ui-3_dev/single/cursor-auto-002/format/html5/ https://test.csswg.org/harness/test/css-ui-3_dev/single/cursor-auto-003/format/html5/ What is the expected behavior? The tests should pass What went wrong? the test fail Did this work before? No Does this work in other browsers? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: OS X 10.11.6 Flash Version: The "auto" behavior of the "cursor" property used to be only vaguely defined, but to improve interoperability, the latest specification[1] is more clear: > auto behaves as 'text' over text, and 'default' otherwise. Other expected effects, such as the pointer cursor overlinks should be achieved using the UA stylesheet, rather than through the magic behavior of the "auto" value. Chrome uses "auto" rather than the UA stylesheet to adjust the cursor, which causes the test mentioned above to fail. [1] https://drafts.csswg.org/css-ui-3/#valdef-cursor-auto This is related to https://bugs.chromium.org/p/chromium/issues/detail?id=737452, but this is about links, and that is about form controls.
,
Jun 29 2017
Confirmed test failure on Linux Chrome 59, 60 and 61.
,
Jun 29 2017
This really belongs to UI>Input component.
,
Jul 13 2017
This is similar to crbug.com/737452 , should we merge them?
,
Jul 13 2017
Sure.
,
Jul 14 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jun 28 2017