This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Since due to sniffing text/html can turn out to be a feed (and actually application/xml as well) there needs to be some way for this to plug back into registerContentHandler() because otherwise e.g. bloglines.com cannot become a proper feed reader. Of course, browsers can give users some UI on how to let a Web page be a feed reader, but that seems more cumbersome and goes against the idea of having registerContentHandler() in the first place.
I just need to make it clearer that the registered types are compared after the sniffing. (It's already mentioned, but very subtly.) Could also mention the handlers earlier in the navigation algorithm for schemes. Also, should probably clarify that the navigation is restarted with the new URL if the UA is willing to just go ahead and navigate to the registered URL.
Tim also notes that this doesn't provide us with a way to do namespace-based dispatching, e.g. if a feed is sent as text/xml. Do UAs today just sniff for that case, or do they use their XML handling?
This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.