Open Bug 988842 Opened 10 years ago Updated 2 years ago

Remove chromeOnlyContent infrastructure (freeing up 2 node bits)

Categories

(Core :: DOM: Core & HTML, defect, P5)

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
macOS
Type:
defect

Tracking

()

People

(Reporter: bholley, Unassigned)

References

Details

I was going to do this in bug 986730 (see bug 986730 comment 0), but I ran into snags (see bug 986730 comment 1). Somebody needs to go through and sort out this whole mess, which will allow us to remove the concept of CHROME_ACCESS_ONLY, and free up some node bits.
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.