4 ms·
I don't think you understand the technical applications that the website is advocating for. I can appreciate that the technicalities are frustrating, but the we
by catapart 1y ago
I don't think you understand the technical applications that the website is advocating for. I can appreciate that the technicalities are frustrating, but the web works the way it works, for better or worse.
- whstl 1y agoNope. I am saying the web should work the way it is, like Hacker News does, as I already have brought up elsewhere. You are saying "tab headers, buttons, or even text-sparse tiles [...] should, prevent text selection". The article is saying the same thing I am. Basically don't do `user-select: none;`. The example is itself in the article's CSS.
- catapart 1y ago[flagged]
- whstl 1y agoYou are the one saying it breaks keyboard usage, and still haven't given an example of why and how.
- catapart 1y ago[flagged]
- whstl 1y agoYou can do better than doing personal attacks. The article is not advocating for breaking anything. And unlike me you haven't provided a single example so far, only workarounds for people who don't like your suggestions.
- catapart 1y ago[flagged]
- whstl 1y agoYou provided an example with anchors. In your original post you say "But stuff like tab headers, buttons, or even text-sparse tiles - things meant for the user to click on - can, and usually should, prevent text selection" and you explicitly mention that you leave out anchors. So far no reply to me has talked about problems causing by having selectable "tab headers, buttons, or even text-sparse tiles". I am still 100% open to hearing about it. But I can do away with the personal attacks and sarcasm.
- dang 1y agoYou broke the site guidelines quite badly in this thread, including (such as here) with personal attacks. Could you please review them and stick to them in the future? We'd appreciate it. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html