One other angle yet mentioned: JS is browser native. No matter how slow it is, browser is now the LCD. Similar server-client codebase, while ugly, is another plus.

I think the hack is to store html height/width locally and restore it as early as possible so the content will then load under the scrolled view

Oh hey, a fellow noticing person!

yes, and the bar is not at all at the same level.

Now ui libraries does its own reset. The no-nonsense blogger just use a few styling, and yeah, the default now is good enough.

Back in the day I requested chrome feature "copy text" in addition to "copy link" on <a> context menu. Now I tried it it's no longer there.

It's not? Just checked a Chrome instance I had handy, it has all three options in the context menu - "Copy", "Copy link address" and "Copy link to highlight". First one copies text in between <a> ... </a>, second one copies the href attribute, and third one copies the link to page you're on with that weird URL framgment-based arbitrary text anchor/highlight scheme.

All three work on Google search results for me.

Maybe weird behavior on my end? Or perhaps you need to select part of <a>'s content to trigger it?

Recently I've been considering simple click-to-copy button is a bad ux since it can destroy one's clipboard (granted, I'm not using clipboard manager). This might be mitigated with a confirmation before actually replacing the clipboard, but I haven't encountered such implementation. Maybe due to ctc more often appear in tech-related websites.

Instead of click-to-copy, you could do click-to-highlight, so that "right-click > Copy" highlights the text on right-click if it's not initially selected. There is some subtlety in the logic, because it shouldn't interfere when the user manually selects a substring.

For a demo of click-to-highlight, install IPvFoo and use your mouse in the popup window. See the 'selectWholeAddress' function in https://github.com/pmarks-net/ipvfoo/blob/master/src/popup.j...

I'm aware of that gesture, but I think it shows the point that it requires extra intention from the user to do select+copy on an input-looking field with copy button attached, instead of being part if the default ctc button experience.

Not that I am searching, but I wonder if there's already tog/nielson/other ux research on this specific interaction.

More OSs should adopt X11 paste from the primary selection. It can safely coexist with a regular clipboard.

I highly recommend getting a clipboard manager! They keep a (usually configurable) history of your most recent clipboard items and allow switching the active selection between them.

Surely. First time I used clipboard management was long time ago somewhen in windows xp era. But growing older make me not really incentivized on trying myself to relearn clipboard history gestures. I might do that someday though.

The difference is now I know git and text editor with hot-save support; with mostly textual clipboard, the texts usually just land in either git/editor.

So far the alternatives to capricious developer choices are:

- Draw Chinese characters into a translator

- Just have every website support every language ever

- Install cliboard manager software to handle the fact you don’t always want to copy

Gotta love HN.

It's frustrating that sharing workarounds in good faith attracts drive-by snark like this comment.

I don't want a good-faith workaround for a website hijacking my clipboard. I want the website and its developers to stop doing things that are stupid and wrong.

I don't disagree! But as long as they continue to do stupid and wrong things, workarounds remain useful.

Here's my recent favorite UI for ID numbers

Hover shows icon for copy rich link Clicking shows menu with copy plain text, copy rich link, search for backlinks, etc Element itself is a link that can be ⌘-clicked, right clicked etc

Another part are malleable memory. Something I imagine we as humans are accumulating context daily and doing reinforcement training while we sleep.

It seems like it would be more stable to run windows office under wine instead.

I think it is due to java already featured the threadlocal mechanism so the ecosystem get used to it. I just recently rediscovering java (w/o framework) when virtual thread landed and I gravitated towards context passing. Even more recently I started reading golang code only to then seeing they were doing the same thing.

Also many are still using the og 1987 version