Closed
Bug 210601
Opened 21 years ago
Closed 21 years ago
DOM XPath from chrome:// throws NS_ERROR_DOM_PROP_ACCESS_DENIED
Categories
(Core :: XSLT, defect)
Core
XSLT
Tracking
()
RESOLVED
FIXED
People
(Reporter: axel, Assigned: caillon)
Details
(Keywords: regression)
Attachments
(1 file)
|
1.69 KB,
patch
|
axel
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
caillon regressed URIUtils::CanCallerAccess for chrome content in bug 163645. Not sure which other callers of nsScriptSecurityManager::CheckSameOriginPrincipal rely on getting access from chrome here, I can see at least two others. Didn't test if this affects p3p, too. But I guess it does.
|
Assignee | |
Comment 1•21 years ago
|
||
|
Reporter | |
Comment 2•21 years ago
|
||
Comment on attachment 126442 [details] [diff] [review] Fix the caller r=axel@pike.org. We might wanna ask the subjectPrincipal for UNIVERSAL_BROWSER_READ, could you add that to the comment?
Attachment #126442 -
Flags: review+
|
|
Assignee | |
Updated•21 years ago
|
Attachment #126442 -
Flags: superreview?(jst)
|
|
Assignee | |
Comment 3•21 years ago
|
||
I think that's a subject for a different bug. This just adds the local check you need (and implicitly, though wrongly got with the same origin check before).
Status: NEW → ASSIGNED
|
||
Comment 4•21 years ago
|
||
Comment on attachment 126442 [details] [diff] [review] Fix the caller sr=jst
Attachment #126442 -
Flags: superreview?(jst) → superreview+
|
|
Assignee | |
Comment 5•21 years ago
|
||
Fixed
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•