Closed Bug 444224 Opened 16 years ago Closed 6 years ago

Get scriptblockers in a better state

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: sicking, Unassigned)

References

Details

This is a tracking bug to make sure that we have scriptblockers (nsContentUtils::Add/RemoveScriptBlocker) into a state where we're more comfortable with that we're protecting enough code paths, and that we don't execute script during any parts of those code paths.
Flags: blocking1.9.1+
Marking this one as a P1, though the individual dependencies are lower priority. Many of them are likely triggered by the same problem though.
Flags: blocking1.9.1+ → wanted1.9.1+
Priority: -- → P1
Assignee: nobody → jonas
Depends on: 412623
No longer depends on: 412623
No longer blocks: 466057
Depends on: 466057
Depends on: 472189
Severity: normal → major
Priority: P1 → P2
Do we still have work to do here, Olli? Still 4 dependencies here.
Assignee: jonas → nobody
Flags: needinfo?(bugs)
I guess need to check if those dependencies are still valid. But this is so old, that I expect that we should just close this. We've change the setup quite a bit and most of the relevant assertions are now MOZ_ASSERTs which crash on debug builds.
Couldn't reproduce the issues in the dependency bugs. If there are some issues, better to file new bugs.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(bugs)
Resolution: --- → INCOMPLETE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.