@wanderview hey Ben! Am I missing something here or is this still an issue? Seems like an important one for mobile especially PWAs, etc. https://bugzilla.mozilla.org/show_bug.cgi?id=251784#c10 …
Well, it sure would be nice if they described what they do so we can consider standardizing it instead of everyone having to reverse-engineer everyone else! Again, what Firefox does right now is what the HTML spec says to do...
-
-
Apparently here's the actual code in Chromium: https://chromium.googlesource.com/chromium/blink/+/5da5b59/Source/core/loader/FrameLoader.cpp#1049 …
-
Right, we can try to reverse-engineer that code (e.g, its concept of "load complete", its m_loadType, etc, etc). Or the Chrome folks could document the behavior in terms of spec concepts, not internals that may not match any concepts in the spec or in other browsers...
- 4 more replies
New conversation -
-
-
I get that and agree. But also, from the perspective of making it simple to build PWAs and SPAs without having to mess with building mechanisms for persisting scroll position it sure is nice.
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.