This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html Multipage: http://www.whatwg.org/C#navigate-fragid-step Complete: http://www.whatwg.org/c#navigate-fragid-step Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html Comment: Avoid manual redirect flag somehow. Posted from: 82.130.78.175 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:30.0) Gecko/20100101 Firefox/30.0
My thinking is this. Per bug 24375 redirects have to be atomic. Apart from AppCache which will likely die this is the only feature in the platform that seems to need a bit more control over redirects. I'd like to put this into Fetch somehow so we can remove the manual redirect flag.
I don't see why appcache would die. It's used and implemented, and anything that follows it would have to have similar logic anyway to handle captive portals. As far as navigation goes, how do you propose to remove the logic? You want to put navigation into fetch?
Why would I need to include all of navigate? It seems only a very small part of the algorithm uses it, and it's not clear to me why it needs it.
What would fetch do if you tried to fetch an HTTP URL that redirected to a mailto: URL, without the manual redirect steps?
It would return a network error.
Although that would depend in part on how we resolve bug 24091 of course.
If it returns a network error, I can't use it. Navigation needs to actually support it. That's why I use the manual redirect mode...
The current algorithm also seems to result in a network error, unless the scheme is not a supported scheme, but what that means is not really defined.
mailto: to a native app, right now, would be handled by the "If the new resource is to be handled using a mechanism that does not affect the browsing context, e.g. ignoring the navigation request altogether because the specified scheme is not one of the supported protocols, then abort these steps and proceed with that mechanism instead" step.
Okay, so this won't work. Scoping it down to navigation is something to keep in mind for later I guess.