Bug 98408 - Clarify the "unsafe JavaScript attempt to access ..." message.
: Clarify the "unsafe JavaScript attempt to access ..." message.
Status: NEW
: WebKit
WebCore Misc.
: 528+ (Nightly build)
: Unspecified Unspecified
: P2 Normal
Assigned To:
:
:
: 43504
: 97978
  Show dependency treegraph
 
Reported: 2012-10-04 07:49 PST by
Modified: 2012-10-04 07:50 PST (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2012-10-04 07:49:23 PST
Report from a user, with regard to the "Unsafe JavaScript attempt to access frame with URL $X from frame with URL $Y. Domains, protocols and ports must match." console warning:  "What was accessed? What was unsafe about it? Which one(s) of domain, protocol, and port didn't match? Why does this error spam the console in apps (e.g. Gmail) that continue to work perfectly?"

We've made a few changes to this (sandboxing, for example), but we can certainly do more to provide some context. This at least partially overlaps with 43504.
------- Comment #1 From 2012-10-04 07:50:48 PST -------
Two users specifically complained about Vimeo's player generating this error, might be a good place to start.