Closed
Bug 1764370
Opened 3 years ago
Closed 3 years ago
Use NS_GET_IID instead of NS_DEFINE_IID for PRIVATE_IDBREQUEST_IID
Categories
(Core :: Storage: IndexedDB, task)
Core
Storage: IndexedDB
Tracking
()
RESOLVED
FIXED
101 Branch
Tracking | Status | |
---|---|---|
firefox101 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
Details
Attachments
(1 file)
IndexedDB uses PRIVATE_IDBREQUEST_IID as a special internal IID when QIing. To actually use that IID, it uses NS_DEFINE_IID in each file that uses it. This has been the deprecated way to do this for 20 years or so, and this is the last remaining use of it in the tree. I've written a patch to replace the use of it with NS_DEFINE_IID by creating an empty class to hang the special IID off of. This is the same thing that the cycle collector does for its special interface, via the class nsCycleCollectionISupports.
Assignee | ||
Comment 1•3 years ago
|
||
Create a new fake class so that NS_GET_IID can be used instead of
NS_DEFINE_IID.
Pushed by amccreight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1a81dca11365
Use NS_GET_IID instead of NS_DEFINE_IID for PRIVATE_IDBREQUEST_IID. r=dom-workers-and-storage-reviewers,asuth
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox101:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•