The X-Frame-Options not being defined issue is https://github.com/whatwg/html/issues/1230. I would have preferred if blocking was effectively a network error (no event currently and cross-origin), but it seems other browsers might have taken that opportunity away from us and so now it needs to be about:blank coupled with a `load` event? I guess that's fine. (I mentioned that likely resolution in the issue.)
Bug 1599256 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The X-Frame-Options not being defined issue is https://github.com/whatwg/html/issues/1230. <s>I would have preferred if blocking was effectively a network error (no event currently and cross-origin), but it seems other browsers might have taken that opportunity away from us and so now it needs to be about:blank coupled with a `load` event? I guess that's fine. (I mentioned that likely resolution in the issue.)</s> Given Mike's recent comment there treating this as a network error seems good. It appears that Chrome might still dispatch a `load` event for such errors though. Aligning with that seems reasonable. I don't think that creates a new communication channel, but it will nix the idea for an `error` event (issue 125 mentioned in comment 9).
The X-Frame-Options not being defined issue is https://github.com/whatwg/html/issues/1230. <strike>I would have preferred if blocking was effectively a network error (no event currently and cross-origin), but it seems other browsers might have taken that opportunity away from us and so now it needs to be about:blank coupled with a `load` event? I guess that's fine. (I mentioned that likely resolution in the issue.)</strike> Given Mike's recent comment there treating this as a network error seems good. It appears that Chrome might still dispatch a `load` event for such errors though. Aligning with that seems reasonable. I don't think that creates a new communication channel, but it will nix the idea for an `error` event (issue 125 mentioned in comment 9).
The X-Frame-Options not being defined issue is https://github.com/whatwg/html/issues/1230. <del>I would have preferred if blocking was effectively a network error (no event currently and cross-origin), but it seems other browsers might have taken that opportunity away from us and so now it needs to be about:blank coupled with a `load` event? I guess that's fine. (I mentioned that likely resolution in the issue.)</del> Given Mike's recent comment there treating this as a network error seems good. It appears that Chrome might still dispatch a `load` event for such errors though. Aligning with that seems reasonable. I don't think that creates a new communication channel, but it will nix the idea for an `error` event (issue 125 mentioned in comment 9).
The X-Frame-Options not being defined issue is https://github.com/whatwg/html/issues/1230. Given Mike's recent comment there treating this as a network error seems good. It appears that Chrome might still dispatch a `load` event for such errors though. Aligning with that seems reasonable. I don't think that creates a new communication channel, but it will nix the idea for an `error` event (issue 125 mentioned in comment 9).