Bug 69236

Summary: Browsing context name seems to take frame id into account, when per spec it should not
Product: WebKit Reporter: Boris Zbarsky <bzbarsky>
Component: FramesAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Testcase none

Boris Zbarsky
Reported 2011-10-02 22:17:05 PDT
Created attachment 109436 [details] 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.
Attachments
Testcase (420 bytes, text/html)
2011-10-02 22:17 PDT, Boris Zbarsky 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2011-10-03 12:37:34 PDT
*** This bug has been marked as a duplicate of bug 11388 ***
Note You need to log in before you can comment on or make changes to this bug.