Does it strike anyone else as odd how hard it is to show a DOM list of 10,000 nodes in a performant way? Seems like a missing web primitive
-
-
suspect the perf benefit > outweighs 1k LOC :) Also: a11y, focus, grid, var height items, virtualization, x-browser.
-
: yeah,
@samccone isn't disputing that. He's only asking for a standardised version. We've illuminated some of the complexity = )
End of conversation
New conversation -
-
-
a11y tools have a similar dilemma, e.g. "here is a giant spreadsheet most of which remains on the server"
-
... where most ATs assume the entire DOM is available and provide their own search/jump-to mechanisms.
End of conversation
New conversation -
-
-
The first time I saw an infinite scroll list that reused DOM nodes I though "awesome! wait, how do I find what I want if it's not in DOM?"
-
Often I'd rather wait longer to load a static page and have full text search than use a "fancier" page with a custom search solution.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.