_parent named browsing context should not be case-sensitive
Reported by
l...@bocoup.com,
Mar 16 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. window.open a document into `_pARent` What is the expected behavior? The browser should choose the parent browsing context if the current context has a parent, or choose the current browsing context if it is a top-level browsing context. What went wrong? The browser is opening a new browsing context named `_pARent`. Any subsequent calls to `window.open` into `_pARent` will reuse the browsing context created by the first invocation. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 56.0.2924.87 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 25.0 r0 Relevant HTML spec section 7.1.5: https://html.spec.whatwg.org/#browsing-context-names Relevant web-platform-tests: https://github.com/w3c/web-platform-tests/pull/5150 Likely related to https://bugs.chromium.org/p/chromium/issues/detail?id=702178
,
Mar 17 2017
Reporter@ - Thanks for filing the issue...!! Could you please provide a sample html file to test this issue. This will help us in triaging the issue further. Thanks...!!
,
Mar 20 2017
Follow the HTML issue for updates, this might not be a bug - https://github.com/whatwg/html/issues/2443
,
Mar 27 2017
Concluded in https://github.com/whatwg/html/issues/2443#issuecomment-289043039 that case-insensitive is better.
,
Mar 27 2017
,
Mar 30 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rsesek@chromium.org
, Mar 16 2017