Remove the classinfo for DOMWindowUtils

RESOLVED FIXED in mozilla32

Status

()

defect
RESOLVED FIXED
5 years ago
3 months ago

People

(Reporter: Ehsan, Assigned: Ehsan)

Tracking

(Blocks 1 bug)

unspecified
mozilla32
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Assignee

Description

5 years ago
No description provided.
Assignee

Updated

5 years ago
Assignee: nobody → ehsan
Assignee

Comment 2

5 years ago
Comment on attachment 8431078 [details] [diff] [review]
Remove the classinfo for DOMWindowUtils

https://tbpl.mozilla.org/?tree=Try&rev=2739094b9ab1

I've fixed the test failures after pushing to try.

Note that I removed test_bug397571.html because I don't think that test makes sense any more, as the DOMWindowUtils object should not be accessible to content.
Attachment #8431078 - Flags: review?(bzbarsky)
Comment on attachment 8431078 [details] [diff] [review]
Remove the classinfo for DOMWindowUtils

Nice.  Sounds like that specialpowers stuff is working.  ;)

r=me
Attachment #8431078 - Flags: review?(bzbarsky) → review+
Assignee

Comment 4

5 years ago
Either that, or I had an extremely lucky one here! :-)
Assignee

Updated

5 years ago
Blocks: stdglobal
Assignee

Comment 6

5 years ago
So, can we now remove the security checks in nsDOMClassInfo?
Flags: needinfo?(bzbarsky)
I'm actually not sure.  Bobby?
Flags: needinfo?(bzbarsky) → needinfo?(bobbyholley)
Probably. Which ones are you referring to? Feel free to write a patch and ask me for review.
Flags: needinfo?(bobbyholley)
https://hg.mozilla.org/mozilla-central/rev/c7a5fd3f26e9
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Assignee

Updated

5 years ago
Blocks: 1018482
(In reply to :Ehsan Akhgari (lagging on bugmail, needinfo? me!) from comment #6)
> So, can we now remove the security checks in nsDOMClassInfo?

From bug 1018482, I'm assuming you meant nsDOMWindowUtils here.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.