- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Oct 2017 09:32:22 +0000
- To: public-css-archive@w3.org
> Also, since what is considered editable might vary per platform (for example, an input type="color" might be a textbox in some browser, hence editable, and a button in another, hence not editable): what value should authors use if they want to specify a custom cursor on that element with a fallback cursor? I suppose they could do `input[type="color"]:read-write`, so I do not the ability to express this with regular selectors and regular values is blocking. However, the argument that we already have interoperability on auto looking like text over editable things is for me a convincing argument. If other browsers agree and want to preserve that, I'm ok with a spec edit. > Another interesting case I found while investigating the WantArrowCursor flag is that we do not show a text-beam cursor on already-selected text but the default arrow instead (presumably to indicate the user can right-click to open the context menu). I would rather have this behavior stay per-spec. I am not sure who to cover that one. I think it could be considered allowed under this part of the spec: > User agents may also ignore the cursor property and display a cursor of their choice to indicate various states of the UA’s user interface, such as a busy cursor when the page is not responding, or a text cursor when the user is performing text selection. but that feels a bit like a stretch. Any suggestion? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1598#issuecomment-336074642 using your GitHub account
Received on Thursday, 12 October 2017 09:32:20 UTC