Get rid of NS_NewDOMStorageEvent

RESOLVED FIXED in Firefox 53

Status

()

Core
DOM
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: baku, Assigned: baku)

Tracking

unspecified
mozilla53
Points:
---

Firefox Tracking Flags

(firefox53 fixed)

Details

Attachments

(1 attachment, 2 obsolete attachments)

Comment hidden (empty)
(Assignee)

Comment 1

a year ago
Created attachment 8818482 [details] [diff] [review]
storage2.patch

No real needs for this patch but it looks cleaner to have it.
Assignee: nobody → amarchesini
Attachment #8818482 - Flags: review?(bugs)
(Assignee)

Comment 2

a year ago
Created attachment 8818483 [details] [diff] [review]
storage2.patch
Attachment #8818482 - Attachment is obsolete: true
Attachment #8818482 - Flags: review?(bugs)
Attachment #8818483 - Flags: review?(bugs)
Comment on attachment 8818483 [details] [diff] [review]
storage2.patch

This initializes the event, but it should stay in uninitialized state.
See other ::Constructor usage in ::CreateEvent.
Attachment #8818483 - Flags: review?(bugs) → review-
(Assignee)

Comment 4

a year ago
Created attachment 8818861 [details] [diff] [review]
storage2.patch
Attachment #8818483 - Attachment is obsolete: true
Attachment #8818861 - Flags: review?(bugs)

Updated

a year ago
Attachment #8818861 - Flags: review?(bugs) → review+

Comment 5

a year ago
Pushed by amarchesini@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/eeeab0b92c12
Get rid of NS_NewDOMStorageEvent, r=smaug

Comment 6

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/eeeab0b92c12
Status: NEW → RESOLVED
Last Resolved: a year ago
status-firefox53: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in before you can comment on or make changes to this bug.