Just to clarify again, I'm ok either way since the impl concern on the performance is gone, thanks to Rossen and your advice on the conf call, but I didn't understand what you wrote and appreciate clarification: > If you have a contenteditable element (or an element that's editable for other reasons) that's a child of a user-select:none element, in all browsers: > > * the editable element and its descendants are selectable This can be achieved by a UA stylesheet: ```css [contenteditable] { user-select-inside: text; user-select-outside: contain; } ``` no? Is it only our assumption of the above UA stylesheet was different, or did I miss anything? -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/336#issuecomment-247226851 using your GitHub accountReceived on Thursday, 15 September 2016 03:49:00 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:03 UTC