-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does any browser still implement namespace-based dispatching? #2656
Comments
If we fix #2657 this might be less problematic. We just end up generating a garbage document and potentially a garbage window. |
It also seems this would require waiting for a root element to be found, which can potentially be a long time, before switching from the old to the new document. That seems problematic (and is not really accounted for event loop wise, as nothing says to go in parallel). |
I don't think Blink has the namespace dispatch. |
It's not implemented and complicates navigation. Closes #2656.
Firefox used to do this with RSS documents, I think? Before removing native RSS support. Could someone confirm it doesn't do it with any other types of XML documents? It'd be ideal to get Safari to weigh in as well, just in case. |
I think Waterfox still suports RSS, so @MrAlex94 might know about that. |
I did ask in Mozilla's |
It's not implemented and complicates navigation. Closes #2656.
In process a navigate response:
In the XML document section:
While the jumping around is by itself worthy of a fix, I'm wondering whether any browser actually does this kind of namespace-based dispatching.
And if such namespace-based dispatching is to take place, should we really do it by creating a document first or just running the XML parser for a bit until we find an element?
The text was updated successfully, but these errors were encountered: