W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

Re: [csswg-drafts] [css-ui] user-select: none and selectionchange event

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Wed, 14 Sep 2016 04:11:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-246901524-1473826297-sysbot+gh@w3.org>
Since both 
[Edge](https://github.com/w3c/csswg-drafts/issues/319#issuecomment-246810440)
 and 
[Chrome](https://lists.w3.org/Archives/Public/public-editing-tf/2016Sep/0002.html)
 intend to match Firefox, and with feedback from multiple people 
involved in js-based editors 
([CKEditor](https://github.com/w3c/csswg-drafts/issues/319#issuecomment-246284727),
 
[Johannes](https://github.com/w3c/csswg-drafts/issues/319#issuecomment-246518652)
 and 
[caub](https://github.com/w3c/csswg-drafts/issues/319#issuecomment-238461847))
 going in the same direction, we have a strong candidate for resolving
 this:

> Attempting to start a selection in an element where 'user-select' is
 ''none'', such as by clicking in it or starting a drag in it, must 
not cause a pre-existing selection to become unselected or to be 
affected in any way.



-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/319#issuecomment-246901524 
using your GitHub account
Received on Wednesday, 14 September 2016 04:11:45 UTC

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