Oh, you are right!

Hmm .. and the approach already shows its weaknesses when I play with it: When I search for something on the page, it gives me twice as many hits as there are. And jumps around two times to each hit when I use the "next" button.

I wonder if that is fixable.

▲

debazel 16 hours ago | parent | next [-]

There is a neat `inert` html attribute you can use to disable all interactions as well as hide the text from ctrl+f searches. (Sadly Safari is the weird one out, and does not exclude the content from searches.)

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

▲

fsfod 14 hours ago | parent | prev | next [-]

GitHub had to solve the same problem when speeding up there code viewer.

https://github.blog/engineering/architecture-optimization/cr...

▲

knallfrosch 17 hours ago | parent | prev [-]

One simply needs the Highlight API. I held back, but now even Firefox ESR supports it.

https://developer.mozilla.org/en-US/docs/Web/API/Highlight

All the trickery vanishes and you get first-class CSS support.

	▲	mg 5 hours ago \| parent \| next [-]
		That works on the text inside a textarea? Is there a demo showcasing this somewhere?
	▲	bakkoting 12 hours ago \| parent \| prev [-]
		And there's an open issue for that already: https://github.com/bearcove/arborium/issues/62