2 ms·
Often it's dysfunction; some stake holder or lawyer, etc., having funded the development of some site, observe that one can 'steal' content with copy+paste and
by topspin 7y ago
Often it's dysfunction; some stake holder or lawyer, etc., having funded the development of some site, observe that one can 'steal' content with copy+paste and freak out, so the front end developers stick this placebo in to shut them up.
There are legitimate use cases; the classic being 'sort a table by clicking on a column heading', where without 'user-select: none;' (or some other mitigation) the column heading will often end up being selected. Often when one creates a site that involves users interacting with text using a traditional pointer device outside of form controls a need for this will appear.
- grammarxcore 7y agoFrom personal experience I've seen it mostly pulled out as a solution to an XY problem. Normal text tags give you the text cursor. If you don't want the text cursor, why not disable selection? The proper solution is to just apply the default cursor. I haven't experienced your situation before but that sounds completely reasonable; many non-web devs I know don't even know about the dev console.
- kevin_thibedeau 7y agoW3C gets the ultimate blame. These attributes should not even exist. They should have put their foot down and said no to Google.