зеркало из https://github.com/mozilla/gecko-dev.git
f4e06d4673
In the case we click a link from inside the frame, we don't want to check for activation from the parent window but ourselves. It feels like using the sourceWindowContext for these checks is always the right thing to do, but it's not always possible if we set the location.href from an out-of-process parent. In this case, we fall back to consuming user activation on the iframe itself. This is tested in browbrowser_protocol_ask_dialog.js when run with fission enabled. We could consider making the user activation stuff more multiprocess-friendly, but it's not clear to me it's worth it for this particular edge case. Differential Revision: https://phabricator.services.mozilla.com/D100578 |
||
|---|---|---|
| .. | ||
| base | ||
| docs | ||
| exthandler | ||
| prefetch | ||
| preload | ||
| moz.build | ||