- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2017 08:03:11 +0000
- To: public-css-archive@w3.org
> Consider <div style="user-select:none">Non-selectable text</div>; I believe user agents should be allowed and encouraged to behave like Firefox and show an arrow cursor over that text. Agreed, and [CSS-UI level 4 calls that out explicitly](https://drafts.csswg.org/css-ui-4/#cursor). But `user-select:none` doesn't exist in level 3, so it is left out. We could do as you suggested, and change "auto behaves as text over text" to "auto behaves as text over selectable text". Even though level 3 doesn't have a mechanism for making text non selectable, that may be a better way to record what we intend. > I would rather not change the logic that computes this WantArrowCursor flag, so to continue to have this stay unchanged we need the behavior of auto to allow user agents to use more of the context than just "Am I over text or not?" and allow to consider selectability and editability. I am not sure I've followed you 100%. I do understand (and agree with) the part about selectability, but I thought you were saying that editability could be handled via the UA stylesheet. Or is that only contentEditable? What other kind of editability cannot be handled in the UA stylesheet? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1598#issuecomment-335722670 using your GitHub account
Received on Wednesday, 11 October 2017 08:02:59 UTC