Bug 169748

Summary: _parent named browsing context should not be case-sensitive
Product: WebKit Reporter: Lyza Gardner <lyza>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: cdumez, phistuck, zcorpan
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=169747
https://bugs.webkit.org/show_bug.cgi?id=170128

Lyza Gardner
Reported 2017-03-16 06:26:01 PDT
(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
Attachments
PhistucK
Comment 1 2017-03-20 03:37:21 PDT
Filed an HTML issue, so this might not be a bug - https://github.com/whatwg/html/issues/2443
Simon Pieters (:zcorpan)
Comment 2 2017-03-27 00:24:12 PDT
Concluded in https://github.com/whatwg/html/issues/2443#issuecomment-289043039 that case-insensitive is better.
Chris Dumez
Comment 3 2017-04-04 20:13:33 PDT
*** This bug has been marked as a duplicate of bug 169747 ***
Note You need to log in before you can comment on or make changes to this bug.