[Webkit-unassigned] [Bug 80205] 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
Tue Mar 13 17:32:44 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=80205





--- Comment #2 from Kentaro Hara <haraken at chromium.org>  2012-03-13 17:32:43 PST ---
Maybe this is not only a problem of frameElement. contentDocument also requires null if the access is not allowed.

http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#dom-iframe-contentdocument

It would make sense to fix code generators to return null when shouldAllowAccessToNode() fails.

-- 
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