4 ms·

> for displaying unselectable static text FTFY (but seriously, why do so many sites do that?!?)

by stronglikedan 1y ago

wiseowise 1y ago
Mobile experience.
- yurishimo 1y ago
  It makes sense in some places; buttons, mostly so quickly tapping a button doesn’t zoom or whatever. I agree that a lot of people are lazy and block text selection sitewide though because it’s easy and makes the PM go away.
  - ajmurmann 1y ago
    If the PM didn't even request it explicitly.
amluto 1y ago
Unselectable static text is so last year. The cool new thing is these funny blue bits of text with click handlers that, when all the stars align, navigate to a different URL. Somewhere on the road map is context menu support, and the ability to open in a new tab is on the will-never-happen wishlist because no one can figure out how to do it in a cross-platform manner. Showing the target URL in a status bar didn’t even make the wish list. The <a> tag is only for retro fanatics. Seriously, I was peeking at the docs for Qwik, one of the cool new supposedly-lighter-weight frameworks the other day, and I was delighted to discover that, in what is obviously intended to resemble ordinary multi-page HTML, the links aren’t links. The long press behavior is utterly, comically wrong. This isn’t even unusual any more. I guess Qwik is proud that the JavaScript needed to emulate links is only 1kb minified and doesn’t add time-to-interactive overhead that scales poorly with page size, but literally every browser has had complete, native, no-script needed support for <a> even if the entire browser was a terminal app! Check it out: https://qwik.dev/docs/getting-started/ https://qwik.dev/docs/getting-started/
- pjmlp 1y ago
  That is crazy.
- rustystump 1y ago
  Wow. That is insane.
- Zanfa 1y ago
  Fake <a> tags are so yesterday. Everybody knows you should actually render all text on a canvas using a custom WebGL renderer for the best UX.

> for displaying unselectable static text FTFY (but seriously, why do so many sites do that?!?)

wiseowise 1y ago

Mobile experience.

yurishimo 1y ago
It makes sense in some places; buttons, mostly so quickly tapping a button doesn’t zoom or whatever. I agree that a lot of people are lazy and block text selection sitewide though because it’s easy and makes the PM go away.
- ajmurmann 1y ago
  If the PM didn't even request it explicitly.

amluto 1y ago

Unselectable static text is so last year. The cool new thing is these funny blue bits of text with click handlers that, when all the stars align, navigate to a different URL. Somewhere on the road map is context menu support, and the ability to open in a new tab is on the will-never-happen wishlist because no one can figure out how to do it in a cross-platform manner. Showing the target URL in a status bar didn’t even make the wish list. The <a> tag is only for retro fanatics. Seriously, I was peeking at the docs for Qwik, one of the cool new supposedly-lighter-weight frameworks the other day, and I was delighted to discover that, in what is obviously intended to resemble ordinary multi-page HTML, the links aren’t links. The long press behavior is utterly, comically wrong. This isn’t even unusual any more. I guess Qwik is proud that the JavaScript needed to emulate links is only 1kb minified and doesn’t add time-to-interactive overhead that scales poorly with page size, but literally every browser has had complete, native, no-script needed support for <a> even if the entire browser was a terminal app! Check it out: https://qwik.dev/docs/getting-started/ https://qwik.dev/docs/getting-started/

pjmlp 1y ago
That is crazy.
rustystump 1y ago
Wow. That is insane.
Zanfa 1y ago
Fake <a> tags are so yesterday. Everybody knows you should actually render all text on a canvas using a custom WebGL renderer for the best UX.