Able to repro this issue on Windows 7, MAC (10.11.6) & Ubuntu Trusty (14.04) for Google Chrome Stable Version - 53.0.2785.143

This is a Non-Regression issue existing from M30 - # 30.0.1549.0

Deleted: 651596.mov 16.8 MB

651596.mov 16.8 MB Download

Yeah. You're right. We're using the generic parsing code here...

I wonder if we should redefine it to match https://drafts.csswg.org/cssom-view/#the-features-argument-to-the-open()-method?

Heh.  I had to go out of my way in Gecko to implement what the spec says, fwiw...  If that's not what you meant, that's slightly annoying.  :(

The rules at https://drafts.csswg.org/cssom-view/#the-features-argument-to-the-open()-method don't seem to match either the Gecko or the Blink implementation of normal feature parsing (which also don't match each other, fwiw).  That's because they only spec it for the width/height/left/top feature names, which are int-valued, not bool-valued....  This one is clearly bool-valued, kinda (noopener=0 is treated as "true" in Blink, which is not how other bool-valued things work).

Actually, there is another difference between what the spec says and what Blink does, and a somewhat more serious one.  Consider this:

 var w = window.open("", "", "NOOPENER");
 alert(w);

per spec this should alert "[object Window]", because the spec says that the specific token that triggers noopener behavior is "noopener".  But Blink seems to be doing some sort of case-insensitive something....

Not bindings-related. This is related to how we implement
https://html.spec.whatwg.org/#apis-for-creating-and-navigating-browsing-contexts-by-name

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot