Does Ctrl-F work like it usually would? (It looks through all content instead of only visible)
-
-
-
Are you asking about <virtual-scroller>? It’s just an example, but… here’s the demo: https://valdrinkoshi.github.io/virtual-scroller/ …
End of conversation
New conversation -
-
-
Won’t this widen the gap between browsers consistency wise?
-
Every new feature added to the web platform already does that today, with a much more complicated polyfilling story. Layered APIs would improve the situation, IMHO.
End of conversation
New conversation -
-
-
What's the state of this proposal and virtual-scroller's proposal? Is it approved already? If so, are there any target versions or something?
-
These are still early-stage proposals. Follow https://www.chromestatus.com/feature/5673195159945216 … and https://www.chromestatus.com/feature/6428344899862528 … to track implementation progress on these two individual LAPIs.
End of conversation
New conversation -
-
-
Why is the fallback in the same string? It could be prone to typos. I would prefer this syntax: <script type="module" src="std:virtual-controller" fallback="https://example.com/virtual-scroller.mjs …" ></script> Or can you pipe with multiple fallbacks?
-
How would that work for static import, i.e. the second example?
- 1 more reply
New conversation -
-
-
I've always been curious about the performance impact of JS objects added by new JS/browser APIs. Is it significant?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
How usable is this really? everywhere I import something I have to pick the fallback repeatedly? how do I author reusable components? (allowing the consumer to specify polyfills/fallbacks)? it feels like an aspect oriented approach would work considerably better
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
Layered APIs
Don’t pay for functionality you don’t use
Built-in polyfill support