There is work in this direction, @domenic or @stubbornella will know status:
https://github.com/WICG/virtual-scroller/blob/master/README.md …
https://www.chromestatus.com/feature/5673195159945216 …
-
-
Replying to @slightlylate @chofter and
Has there not been enough requests for this in the past 5 years that this feature has been absent? Since you have been such an outspoken advocate for performance web, this seems like low hanging fruit for chopping away MBs of JS to synthetically reproduce this capability today
2 replies 1 retweet 2 likes -
-
Replying to @dalmaer @slightlylate and
Without JavaScript or Web Components. My apologies for not being more clear.
1 reply 0 retweets 1 like -
-
Ill try to reframe my question! I'm super aware of the ongoing activities to solve these similar problems. Original question: was there not enough customer ask in between now and 5 years ago, to warrant designing aforementioned API's? This is curiosity about process too.
1 reply 0 retweets 2 likes -
Replying to @TheLarkInn @domenic and
You might phrase this question as an email to your peers over in
@MSEdgeDev who are working with us and the broader community to move designs forward. Doing features via standards is hard, slow, and (apparently) thankless work.3 replies 1 retweet 25 likes -
Replying to @slightlylate @TheLarkInn and
Great to hear that you are all teaming up to get this done. The real questions are: 1: Is there a single person responsible to drive this? If not, can that be fixed? 2: What can be done to accelerate it? What roadblocks can be removed?
1 reply 0 retweets 1 like -
Replying to @chofter @slightlylate and
Things like this are never done by one person. That said,
@flackrw is driving engineering. I’m the Chrome PM. On the Microsoft side there are a bunch of great engineers and@gregwhitworth PMing. It’s a really hard problem because anything we ship *has to* work for frameworks.2 replies 0 retweets 11 likes -
Replying to @stubbornella @slightlylate and
Perhaps the need for comms between companies is a factor here. Could both companies perhaps get their teams together on site for a couple of weeks and just hammer out a V1?
2 replies 0 retweets 0 likes
Browser engineers just talking to themselves is how we get misbegotten features! The way we build fit-for-purpose stuff is to discuss with developers in the design process and iterate.
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.