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

@hugoholgersson Unfortunately, what you think is a behavior that is interoperable between Webkit-derived browsers and IE/Edge is in fact not as interoperable as you would believe. The code we have to support for overriding `auto` as `pointer` on links is fragile and it is our best interest right now to either leave it buggy as-is, or to remove it entirely. 
 
https://wptest.center/#/yizue0 (Edge display a text-beam cursor on 22, Chrome a hand-pointer).

Right now `auto` in Edge is completely inconsistent and often acts as `inherit` which is totally against the spec. If I want to change this, I will however break the logic that currently makes cursor:auto display an hand-pointer on links in most cases. Fixing this would require way more work than this issue is worth, so if we have to keep this behavior, Edge will never get fixed.

At this point the question is whether there is a sane-enough behavior that we all can implement that would get us rid of a bunch of terrible code (and then developers would have a predictable experience when using cursor, all browsers would react the same, and we make things better for our users) or we find out there is not and we stay different forever.

We previously resolved we wanted to be interoperable and resolved on a particular solution, but it turns out the text of the spec did not state exactly what the discussion had us think it was, but except if we cannot get consensus on the updated, I would rather not have us revert the previous decision.

Outside this real-implementer-life considerations, I have no idea why someone would manually set `a { cursor: auto }` and I am absolutely not worried this will ever be a problem. This code is broken today, and the proposed fixed would make it consistently broken so that authors can see and fix the issue independently of the browser they use to test their site.

On the other side, if as an author you ever wondered what cursor was being displayed on an element, you had absolutely no way of finding out. With the proposed text (and what Firefox implements) the computed style of an element will always return the value of the cursor that is being displayed, and not "auto" for every single element. Even when you get "auto", you know as an author this is not any random cursor but one of two specific ones. This, I think, is very valuable for authors.

-- 
GitHub Notification of comment by FremyCompany
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1598#issuecomment-336558913 using your GitHub account

Received on Friday, 13 October 2017 20:26:59 UTC