27916 2015-01-28 11:22:55 +0000 Reconsider the load event with window.open("", ...) 2015-09-01 08:50:13 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WORKSFORME https://html.spec.whatwg.org/#apis-for-creating-and-navigating-browsing-contexts-by-name P3 normal Unsorted 1 contributor ian annevk ian mike Ms2ger zcorpan contributor oldest_to_newest 117537 0 contributor 2015-01-28 11:22:55 +0000 Specification: https://html.spec.whatwg.org/multipage/browsers.html Multipage: https://html.spec.whatwg.org/multipage/#apis-for-creating-and-navigating-browsing-contexts-by-name Complete: https://html.spec.whatwg.org/#apis-for-creating-and-navigating-browsing-contexts-by-name Referrer: Comment: Reconsider the load event with window.open("", ...) Posted from: 91.182.76.126 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 117538 1 Ms2ger 2015-01-28 11:26:03 +0000 http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=3386 <!DOCTYPE html> ...<script> var win = window.open('', '', ''); win.onload = function(e) { w(e) }; w(win); </script> does not appear to log a load event in either Firefox or Chrome. However, Firefox appears to dispatch a load event (async, as specced) if you use 'about:blank' rather than ''. Chrome doesn't in that case. 117607 2 ian 2015-01-29 23:06:45 +0000 I think this was an intentional rationalisation, IIRC. Are there pages that depend on not sending the load event? 117616 3 zcorpan 2015-01-30 08:49:53 +0000 This was discovered as part of reviewing a test case. Web compat situation unknown. 118285 4 ian 2015-03-04 18:59:53 +0000 Well, I've reconsidered it, and it seems reasonable to me... Unless there's a compat need, I think we should stick with it...