User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:48.0) Gecko/20100101 Firefox/48.0 Build ID: 20160823121617 Steps to reproduce: The specification for handling navigations during unload has recently changed, as has Chrome's behavior. The specification change is in https://github.com/whatwg/html/pull/1737 (commit https://github.com/whatwg/html/commit/2a11eef8f92b0335328890dc2cb1e281d18553eb). Now not only cross-origin navigations, but all navigations, are blocked during unload. This matches Chrome as of https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/VfItzNe3WO0 (Chrome 54), and Safari as of Safari 9, and it mostly matches Edge (although Edge only passes some of the updated tests). This was previous discussed in Firefox in bug 371360, bug 409888, and bug 401611. At that time, such a blanket-disallow was not web compatible, causing the saga outlined in those bugs. However, it seems times have changed, and it is now web compatible to simplify the model and simply prohibit navigations during unload. Steps to reproduce: Run the new and modified web platform tests at https://github.com/w3c/web-platform-tests/pull/3732 Actual results: Firefox fails the web platform tests Expected results: Firefox should pass the web platform tests
Hi Anne, Could you advice if there's expected timeframe for this? I could work with the team to put it in the queue. Thanks!
It would be good to align with the other browsers, but it's not high priority relative to other bugs. Making more folks familiar with the navigation code would be good though as we'll likely want to tweak that further.