Re: [csswg-drafts] [css-ui-4] Make selection change behavior configurable

In typical native apps, clicking on UI areas does not deselect any previously selected text. I don't quite see why we need a different behavior here.

Why apply `user-select:none` to areas that have nothing selectable anyway, especially if you're still hoping that a user interacting with that area would affect the selection?

Wouldn't your problem be solved if you applied `user-select:none` less aggressively, and let the whole content area be selectable (instead of just the text parts in the content area), keeping `user-select:none` for tool-bars and other UI centric components?

Besides making deselecting easier, this would have additional benefits. In the example you sent, if an image fails to load and the alt text is shown instead, it would not be selectable. What is to be gained by preventing users from selecting that?

GitHub Notification of comment by frivoal
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 3 May 2017 03:09:27 UTC