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

Hi. I feel like I missing a bit of context, so I am not sure I fully 
follow what you're asking, but if I get it right, you think:
- if something is already selected, clicking in a `user-select:none` 
element should not change that selection
- consequently, no js event relating to the selection being changed 
should be fired, since it isn't being changed.

For the first item, I think this is reasonable, but I am not sure it 
should be mandated: if UAs want to do something else (e.g. trying to 
select a user-select:none element cancels the current selection), 
maybe that's ok. Then again, as far as I can tell, all browsers keep 
the selection as it is, so maybe we can indeed specify the status quo.
 Adding something like this to the spec:

> If some part of the document is selected, and the user attempts to 
start a new selection in an element where `user-select` is `none`, the
 existing selection must not be discarded or changed.

On the other hand, regardless of whether we include the requirement 
above or not, if the selection is indeed not changed, I agree no event
 should be fired. But that's out of scope for this spec: this event is
 not defined in css-ui-4, but in [the selection API 
spec](http://w3c.github.io/selection-api/#selectionchange-event). The 
current definition there seem to say what you'd want, but if you want 
clarifications to it, I suggest [filing an issue 
there](https://github.com/w3c/selection-api/issues).

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/319#issuecomment-238435100 
using your GitHub account

Received on Tuesday, 9 August 2016 02:21:57 UTC