69236 2011-10-02 22:17:05 -0700 Browsing context name seems to take frame id into account, when per spec it should not 2011-10-03 12:37:34 -0700 1 1 1 Unclassified WebKit Frames 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 11388 P2 Normal --- 1 bzbarsky webkit-unassigned ap oldest_to_newest 476770 0 109436 bzbarsky 2011-10-02 22:17:05 -0700 Created attachment 109436 Testcase http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#attr-iframe-name is very clear: only the 'name' attribute of the <iframe> affects the browsing context name. Note that Gecko implements the spec behavior and has forever in text/html as far as I know, so I doubt there is a compat risk there. In application/xhtml+xml, Gecko does have a different behavior, so the situation there may be more complicated. The attached testcase demonstrates the problem. 477155 1 ap 2011-10-03 12:37:34 -0700 *** This bug has been marked as a duplicate of bug 11388 *** 109436 2011-10-02 22:17:05 -0700 2011-10-02 22:17:05 -0700 Testcase test.html text/html 420 bzbarsky PCFET0NUWVBFIGh0bWw+CjxodG1sIGxhbmc9ImVuIj4KPGhlYWQ+CjxtZXRhIGh0dHAtZXF1aXY9 IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4KPC9oZWFk Pgo8Ym9keT4KPHRhYmxlPgogIDx0Ym9keT4KICAgIDx0cj4KICAgICA8dGQ+CiAgICAgICA8YSB0 YXJnZXQ9Im1haW5jb250ZW50IiBocmVmPSJodHRwOi8vYXBwbGUuY29tIj5DbGlja2luZyBtZSBz aG91bGQgb3BlbiBhcHBsZS5jb20gaW4gYSBuZXcgd2luZG93PC9hPgogICAgIDwvdGQ+CiAgICAg PHRkPgogICAgICA8aWZyYW1lIGlkPSJtYWluY29udGVudCIgc3JjPSIiIHdpZHRoPSIyMDAiIGhl aWdodD0iMzAwIj48L2lmcmFtZT4KICAgICA8L3RkPgogICAgPC90cj4KICA8L3Rib2R5Pgo8L3Rh YmxlPgo8L2JvZHk+CjwvaHRtbD4K