169748 2017-03-16 06:26:01 -0700 _parent named browsing context should not be case-sensitive 2017-04-04 20:13:33 -0700 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 169747 https://bugs.webkit.org/show_bug.cgi?id=169747 https://bugs.webkit.org/show_bug.cgi?id=170128 P2 Normal --- 1 lyza webkit-unassigned cdumez phistuck zcorpan oldest_to_newest 1288538 0 lyza 2017-03-16 06:26:01 -0700 (Likely related to https://bugs.webkit.org/show_bug.cgi?id=169747 ) Browsing context name keywords should not be case-sensitive (https://html.spec.whatwg.org/#browsing-context-names). Steps to reproduce issue: 1. `window.open` a document into `_pARent` Expected behavior: Browser should choose parent browsing context, if one available, or current browsing context if current is a top-level browsing context. Actual behavior: Browser creates a new browsing context (i.e. tab/window) Browser appears to be choosing a new, not-previously-existing, non-keyword browsing context when given `_pARent` Subsequent calls to `window.open` into `pARent` are reusing the new browsing context created by the first invocation Related web-platform-tests tests: https://github.com/w3c/web-platform-tests/pull/5150 1289457 1 phistuck 2017-03-20 03:37:21 -0700 Filed an HTML issue, so this might not be a bug - https://github.com/whatwg/html/issues/2443 1291417 2 zcorpan 2017-03-27 00:24:12 -0700 Concluded in https://github.com/whatwg/html/issues/2443#issuecomment-289043039 that case-insensitive is better. 1294337 3 cdumez 2017-04-04 20:13:33 -0700 *** This bug has been marked as a duplicate of bug 169747 ***