[Webkit-unassigned] [Bug 80205] New: window.frameElement should return null if there isn't the Element for the browsing context container
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Mar 2 21:06:48 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=80205
Summary: window.frameElement should return null if there isn't
the Element for the browsing context container
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
URL: http://www.whatwg.org/specs/web-apps/current-work/mult
ipage/browsers.html#dom-frameelement
OS/Version: Unspecified
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: HTML DOM
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: tsuyuhara-syoichi at hotmail.co.jp
CC: morrita at google.com
see http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#navigating-nested-browsing-contexts-in-the-dom .
>window . frameElement
>Returns the Element for the browsing context container.
>
>Returns null if there isn't one.
>
>Throws a SecurityError exception in cross-origin situations.
Internet Explorer 9.0.5, Firefox Nightly 13.0a1(buildID 20120302031112), Opera Next 12.00 alpha(build 1317) return null, but WebKit r109602 returns undefined, on Windows 7 Home Premium SP1 64bit.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list