3 ms·
If you care for "user-select: none", you might be surprised to know that there wasn't an official spec for it to help the browsers interoperably converge, and y
by frivoal 12y ago
If you care for "user-select: none", you might be surprised to know that there wasn't an official spec for it to help the browsers interoperably converge, and you might be happy to learn that I just made one:
http://dev.w3.org/csswg/css-ui-4/#content-selection http://dev.w3.org/csswg/css-ui-4/#content-selection
- jscheel 12y agoAwesome, thanks for submitting that!
- AlexMuir 12y agoLove that standards are being written in the discussion here. As each standard hits 90% I'm going to write a detailed post on the use of them which will go with the email - I've made a start on user-select. I'd be happy to credit you along with a link to this standard if you'd like. Or I'd love to get your feedback on a draft of the article as you seem to be the authority on this! Drop me an email (me@alexmuir.com) if you get a moment.
- frivoal 12y agoI got a moment, so I did drop you a mail:) Thanks for looping me in.
- pc2g4d 12y agoThis is my first exposure to "user-select: none" and it strikes me as a copy control mechanism. Is that the only reason for this, or are their other use cases?
- tekromancr 12y agoOff the top of my head, I could imagine it being useful to prevent accidental selection of text in, say, a paint app or something. *I may be misinterpreting the purpose, however.
- giovannibajo1 12y agoVery useful for kiosks where people interact with a screen and have no clue they are using a maximized browser. Selecting text of labels is not expected in a "native" app