[csswg-drafts] [css-ui][content-selection] Attempting to start a selection in an element where `user-select` is `none`, must cause a pre-existing selection to become unselected. (#9731)

babakfp has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-ui][content-selection] Attempting to start a selection in an element where `user-select` is `none`, must cause a pre-existing selection to become unselected. ==
> 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.

[Go to the quoted text in spec](https://drafts.csswg.org/css-ui/#content-selection:~:text=Attempting%20to%20start%20a%20selection%20in%20an%20element%20where%20user%2Dselect%20is%20none%2C%20such%20as%20by%20clicking%20in%20it%20or%20starting%20a%20drag%20in%20it%2C%20must%20not%20cause%20a%20pre%2Dexisting%20selection%20to%20become%20unselected%20or%20to%20be%20affected%20in%20any%20way).

---

I want to change the above quote to this:

> Attempting to start a selection in an element where `user-select` is `none`, must cause a pre-existing selection to become unselected.

Please take a look at this issue https://bugs.chromium.org/p/chromium/issues/detail?id=1267856.

The reasoning for changing the behavior is, that such behavior results in a bad user experience, because the user is unable to unselect a selection which is an unexpected behavior, since any attempt to unselect a selection such as text must not be prevented.

---

If there is any discussion around this, please let me know about it.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9731 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 December 2023 11:47:17 UTC