Bug 169748 - _parent named browsing context should not be case-sensitive
Summary: _parent named browsing context should not be case-sensitive
Status: RESOLVED DUPLICATE of bug 169747
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-16 06:26 PDT by Lyza Gardner
Modified: 2017-04-04 20:13 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lyza Gardner 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
Comment 1 PhistucK 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
Comment 2 Simon Pieters (:zcorpan) 2017-03-27 00:24:12 PDT 
Concluded in https://github.com/whatwg/html/issues/2443#issuecomment-289043039 that case-insensitive is better.
Comment 3 Chris Dumez 2017-04-04 20:13:33 PDT 

*** This bug has been marked as a duplicate of bug 169747 ***