Re: Issue 74980 in chromium: window.frameElement is not defined

[chro...@googlecode.com]

Updates:
Labels: -Area-Undefined Area-WebKit WebKit-JavaScript

Comment #1 on issue 74980 by stuart...@chromium.org: window.frameElement
is not defined
http://code.google.com/p/chromium/issues/detail?id=74980

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #2 on issue 74980 by sand...@chromium.org: window.frameElement is
not defined
http://code.google.com/p/chromium/issues/detail?id=74980

Would you be able to supply a short snippet of sample code?
Would you have any chance to check the behavior on Safari?

[chro...@googlecode.com]

Updates:
Owner: jap...@chromium.org

Comment #6 on issue 74980 by sand...@chromium.org: window.frameElement is
not defined
http://code.google.com/p/chromium/issues/detail?id=74980

Sounds like a bindings issue. Nate, would you have a look?

Also, permissions across resources are very restrictive if you read from
files rather than URLs (not sure it makes any difference in this case
though - but might be worth a try).

[chro...@googlecode.com]

Comment #8 on issue 74980 by fr...@google.com: window.frameElement is not
defined
http://code.google.com/p/chromium/issues/detail?id=74980

Update: we have seen that when goog.style.getFramedPageOffset(element,
window.top) is called from inside cross-domain iframe,
window.parent.frameElement is null in webkit instead of throwing an
exception according to spec:
http://www.whatwg.org/specs/web-apps/current-work/#navigating-nested-browsing-contexts-in-the-dom

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #9 on issue 74980 by fr...@google.com: window.frameElement is not
defined
http://code.google.com/p/chromium/issues/detail?id=74980

This is related to bug
https://code.google.com/p/chromium/issues/detail?id=17325