W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [css-ui-4] Readonly form control and user-select

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 Jul 2018 16:47:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-407821125-1532537266-sysbot+gh@w3.org>
The Working Group just discussed `Readonly form control and user-select Agenda+ F2F css-ui-4`, and agreed to the following:

* `RESOLVED: Accept florian's proposal`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Readonly form control and user-select Agenda+ F2F css-ui-4<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/285<br>
&lt;dael> florian: Recap: across all browsers afaict when you have editable text area regardles if form control or from contenteditable. When you start selection inside it it can't extend outside. Selection is trapped within<br>
&lt;dael> florian: This behavior is exposed in user-select as contain. Current spec says on editable elements it always does contain. Currently spec as editable content is mutable form controls and contenteditable elements. Moz raised that read-only form controls are not mutable so we should update spec<br>
&lt;dael> florian: Second part is once we do it for normally mutable but currently unmutable switching to user-select: none might be okay. Not clear how editing would work with selection disabled and no one wants to do that.<br>
&lt;dael> florian: So making contain apply to normally mutable but not currently mutable and then making contain switch to none for those.<br>
&lt;dael> florian: Should I wordsmith that into spec or do people think I missed something?<br>
&lt;dael> Rossen: Opinions?<br>
&lt;dael> Rossen: Objections to accepting florian's proposal to the spec?<br>
&lt;tantek> I'd prefer to get Xidorn's opinion<br>
&lt;dael> Rossen: I think it's time to force progress since it's gone through 3 F2Fs.<br>
&lt;tantek> can we discuss in APAC call?<br>
&lt;tantek> otherwise I do not object<br>
&lt;dael> Rossen: tantek xidorn can add his opinion on github.<br>
&lt;dael> florian: We're resolving in favor of his opinion<br>
&lt;dael> tantek: I'm asking that...florian if that's true can you put that into the issue? Just a back and forth to confirm. Why not make sure. You've got wordsmithing, put it in the issue, give xidorn a chance to say yes<br>
&lt;dael> florian: Can I put in PR and merge when he says okay?<br>
&lt;dael> tantek: Sure<br>
&lt;dael> RESOLVED: Accept florian's proposal<br>
&lt;dael> Rossen: Summary is form controls should be selectable?<br>
&lt;dael> florian: More complicated<br>
&lt;dael> florian: I'll create a PR with proposal and merge<br>
&lt;dael> Rossen: We'll look at your PR<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/285#issuecomment-407821125 using your GitHub account
Received on Wednesday, 25 July 2018 16:48:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 25 July 2018 16:48:12 UTC