737085 - Check DOM storage event implementation

Status: RESOLVED INVALID

(Core :: Storage: localStorage & sessionStorage, defect, P5)

Description

[Honza Bambas (:mayhemer)]

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)

Comment 1

[Firefox Bug Husbandry Bot]

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.

Comment 2

[Jens Stutte [:jstutte]]

It seems we changed this quite significantly since then. In particular the switch to use observers should have helped here, I assume.