23857 2013-11-19 09:18:01 +0000 "allowed to navigate" algorithm technically blocks self navigation on sandboxed top-level browsing contexts. 2013-11-19 22:37:56 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED FIXED P2 minor Unsorted 1 bobowencode ian ian mike contributor oldest_to_newest 96504 0 bobowencode 2013-11-19 09:18:01 +0000 Just noticed this minor point. If we have a sandboxed auxiliary browsing context (opened from a sandboxed iframe with allow-popups) and it tries to navigate itself. Following the allowed to navigate algorithm: http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#allowed-to-navigate Our browsing context is A and B, so: 1) A is same as B - move to next step. 2) B is top, but not ancestor of A - move to next step. 3) B is top, not ancestor of A, A is sandboxed and not one permitted sandboxed navigator of B - abort negatively! The simplest fix, as far as I can see, is to add a new step at the start, which simply says "If A is the same browsing context as B, then terminate positively." Also, remove, the now redundant, first condition from the old step 1. 96556 1 ian 2013-11-19 22:24:37 +0000 I made step 3 exclude the case where A=B. 96557 2 contributor 2013-11-19 22:24:56 +0000 Checked in as WHATWG revision r8301. Check-in comment: Always allow a browsing context to navigate itself. http://html5.org/tools/web-apps-tracker?from=8300&to=8301 96559 3 bobowencode 2013-11-19 22:37:56 +0000 (In reply to Ian 'Hixie' Hickson from comment #1) > I made step 3 exclude the case where A=B. That, of course, works just as well :) Thanks Ian.