Check DOM storage event implementation

NEW
Unassigned

Status

()

P5
minor
7 years ago
6 months ago

People

(Reporter: mayhemer, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
See bug 727446 comment 18.

Our current implementation is:
- post a single event on a storage change (thread loop available)
- dispatch the event to all applicable windows using a single event instance
- no thread looping is available between each dispatch

Goal of this bug:
- check if a window could manipulate with the event a way that it wouldn't get to windows in the following order of dispatch
- check if this could cause any other kind of problems (deadlocks, cpu exhaustion, information lose)
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
You need to log in before you can comment on or make changes to this bug.