securityerror dom exception: blocked frame xx from accessing yy doesn't point at offending line or script

UNCONFIRMED
Unassigned

Status

()

P5
enhancement
UNCONFIRMED
a year ago
a year ago

People

(Reporter: maggus.staab, Unassigned)

Tracking

56 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [domsecurity-backlog])

(Reporter)

Description

a year ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170622030208

Steps to reproduce:

we can see error messages like 

  SecurityError (DOM Exception 18): Blocked a frame with origin "our.domain.com" from accessing a frame with origin "external-tracking.com" . Protocols, domains, and ports must match

via a frontend error reporting tool. unfortunately we cannot reproduce those errors but can see that this errors happen a lot in different user agent across certain pages of our customers websites.

could the error message provide more information to make chasing the root cause of this error easier?
I think about things like...
- frame names/ids which are involved
- the concrete line of code or operation which triggered the error


Actual results:

exceptioni occured but not enough information given to reproduce or fix


Expected results:

more information to ease fixing/reproduce
Component: Untriaged → DOM: Security
Product: Firefox → Core
As this is a security exception, I'm surprised this doesn't have the line of code associated with it. If you click the script name-link on the right side of the dev tools console where you see the message doesn't it open the script to the offending line?
Severity: normal → enhancement
Flags: needinfo?(maggus.staab)
(Reporter)

Comment 2

a year ago
I can see this errors only via our error reporting mechanism. I am not able to reproduce the errors
Flags: needinfo?(maggus.staab)
Priority: -- → P5
Summary: securityerror dom exception: blocked frame xx from accessing yy → securityerror dom exception: blocked frame xx from accessing yy doesn't point at offending line or script
Whiteboard: [domsecurity-backlog]
You need to log in before you can comment on or make changes to this bug.