W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2017

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

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 18 Oct 2017 16:45:52 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-337653861-1508345151-sysbot+gh@w3.org>
The Working Group just discussed `auto cursor should behaves as default cursor except for text?`, and agreed to the following resolutions:

* `RESOLVED: Change the definition of cursor auto to look like text over selectable text in css UI 3`
* `RESOLVED: Add exception for editable text into L3 UI`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: auto cursor should behaves as default cursor except for text?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1598<br>
&lt;dael> florian: We've already narrowed problem considerably. It's only about distinguishing things we can't in UA stylesheet. There's two things reopened. WE say one cursor over test, one over everything else. Wee should change that to be one over selectable text. That was in originally, seemed an unintentional omissions<br>
&lt;dael> fremy: I can give some background as to why this is useful. I fyou have text inside a buttonn you don't want the cursor to become a text cursor, but you don't want that. To me it seems straight forward and most browsers are doing this. I think that should be in the spec.<br>
&lt;dael> florian: I sort of have this in L4. In L4 I put an exception to not look like text cursor. I forgot the other things that imght make the text not selectable. [missed]<br>
&lt;dael> Rossen: What is the request?<br>
&lt;dael> florian: For a resolution to change the definition of the auto cursor to change on selectable text, not all text. I'll make edits.<br>
&lt;tantek> and I already +1 that here: https://github.com/w3c/csswg-drafts/issues/1598#issuecomment-335863545<br>
&lt;tantek> last week<br>
&lt;dael> Rossen: That would mean change of behavior...fremy your example. what would the change mean to you?<br>
&lt;dael> fremy: We are already doinng this in edge. I think all browsers also.<br>
&lt;dael> fremy: This is aligning spec with browsers.<br>
&lt;dael> dbaron: Were you going to get to the editable thing?<br>
&lt;dael> florian: I wanted that sep.<br>
&lt;dael> florian: proposed resolution: Change the definition of cursor auto to look like text over selectable text<br>
&lt;tantek> +1 https://github.com/w3c/csswg-drafts/issues/1598#issuecomment-335863545<br>
&lt;dael> Rossen: Objections?<br>
&lt;dael> RESOLVED: Change the definition of cursor auto to look like text over selectable text in css UI 3<br>
&lt;dael> florian: Second part is another thing where we may want to align to browseres, but it contridicts previous intention. In the general case browsers change to text cursor over editable, even if it's not next. This is doable in UA stylesheet, but we're interop in not doing that. There's reluctance to change, esp. on Chrome side. Do we want to change or grant an exception for this because we are interop?<br>
&lt;dael> Rossen: Opinions? Esp from Chrome?<br>
&lt;dael> robertknight_clo_: Do we have anyone from  Chrome?<br>
&lt;dael> s/robertknight_clo_/rossen<br>
&lt;dael> Rossen: I guess there's no one from chrome<br>
&lt;dael> florian: Chrome seemed if other browsers commit to change and we push hard they'll do it. They prob don't want to be alone in this. I'd like to hear from Mozilla.<br>
&lt;dael> dbaron: I'm fine with having editable thing in spec. It's not 100% clear to me that read/write pseudo does the right thing here.<br>
&lt;dael> dbaron: I jut haven't thought through it. I'm  okay with the editable exception.<br>
&lt;florian> tantek: test case: https://test.csswg.org/harness/test/css-ui-3_dev/single/cursor-auto-005/format/html5/<br>
&lt;tantek> +1 similar thoughts to dbaron<br>
&lt;tantek> thanks florian<br>
&lt;dael> fremy: I'm in favor too. It's interop i n all browsers. We can change, but I don't think we need to. I don't think author would expect it and changing something interop could cause problems. My opinion is we should make the change to make things easier for impl.<br>
&lt;dael> Rossen: I hear a lot in favor or don't mind.<br>
&lt;dael> Rossen: Objections to adding an exception into L3 UI?<br>
&lt;tantek> so we're saying auto should look like text over editable text?<br>
&lt;tantek> just trying to understand<br>
&lt;florian> tantek: yes<br>
&lt;dael> RESOLVED: Add exception for editable text into L3 UI<br>
&lt;florian> should -> must<br>
&lt;tantek> +1<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1598#issuecomment-337653861 using your GitHub account
Received on Wednesday, 18 October 2017 16:45:54 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:19 UTC