[csswg-drafts] [css-ui-3] auto cursor should behaves as default cursor except for text?

EiraGe has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-ui-3] auto cursor should behaves as default cursor except for text? ==
The  [spec of "auto" behavior](https://test.csswg.org/harness/test/css-ui-3_dev/single/cursor-auto-005/format/html5/)  says: 

> The UA determines the cursor to display based on the current context


> auto behaves as text over text, and default otherwise

According to the css tests [cursor-auto-005](https://test.csswg.org/harness/test/css-ui-3_dev/single/cursor-auto-005/format/html5/) and [cursor-auto-002](https://test.csswg.org/harness/test/css-ui-3_dev/single/cursor-auto-002/format/html5/) the auto cursor shouldn't change when it's over a text input area or a link. Two chromium bugs were filed by @frivoal :
 [bug 1](https://crbug.com/737452) and [bug 2](https://crbug.com/737458).

I think the the cursor should shows "it's a clickable link" when over a link and I-beam for the input area when it is "auto", because it should change **based on the current context**.  Is the spec wants cursor doesn't show it's over link and over input area?

Also, "auto" is the initial value for cursor style:  [https://drafts.csswg.org/css-ui-3/#cursor](https://drafts.csswg.org/css-ui-3/#cursor). In Chrome, "auto" behave same as cursor style not set. But in Firefox, set "cursor: auto" cursor over link is different from not setting cursor style. 
Should "auto" behave same as style not set?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1598 using your GitHub account

Received on Wednesday, 12 July 2017 18:16:34 UTC