Someone should invent a way for a web server to return a representation of the text, complete with styling and formatting that the browser can use to render it.
Nothing to do with React, it's a common optimization to improve performance with long lists. You only render the dom elements in the viewport, with some buffer. A common technique to achieve that is called "virtualization" or "windowing".
It's common enough that there were a couple browser proposals to deal with this and would address the Ctrl+F issue. I believe this has been merged into the CSS Containment spec, but at the moment it doesn't make windowing obsolete in every situation.
Like GitHub's new code viewer! I have to load the raw text just so I can use Ctrl-F!
Someone should invent a way for a web server to return a representation of the text, complete with styling and formatting that the browser can use to render it.
Twitter does that and I don't understand why. Do they think their js blob can figure out which divs to render faster than the browser engine itself?
I am in no way a front-end person, but my understanding is that it has to do with React and the way it maintains a virtual copy of the DOM.
Having Ctrl-F not work correctly is maddening and I hate it.
Nothing to do with React, it's a common optimization to improve performance with long lists. You only render the dom elements in the viewport, with some buffer. A common technique to achieve that is called "virtualization" or "windowing".
It's common enough that there were a couple browser proposals to deal with this and would address the Ctrl+F issue. I believe this has been merged into the CSS Containment spec, but at the moment it doesn't make windowing obsolete in every situation.
2 replies →