Closed
Bug 1709959
Opened 3 years ago
Closed 3 years ago
Remove chrome-only HTMLImageElement#forceImageState
Categories
(Core :: DOM: Core & HTML, task, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
90 Branch
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: edgar, Assigned: edgar)
Details
Attachments
(2 files)
No one use it per https://searchfox.org/mozilla-central/search?q=forceImageState&path=&case=false®exp=false
And we could also clean up the use of nsImageLoadingContent::ForceImageState a bit.
|
||
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P2
|
Assignee | |
Comment 1•3 years ago
|
||
|
|
Assignee | |
Comment 2•3 years ago
|
||
Depends on D114575
Pushed by echen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/80ad82cfcac7 Part 1: Remove chrome-only HTMLImageElement.forceImageState; r=emilio https://hg.mozilla.org/integration/autoland/rev/a849fcfdead5 Part 2: Remove nsIImageLoadingContent.forceImageState; r=emilio
|
||
Comment 4•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/80ad82cfcac7
https://hg.mozilla.org/mozilla-central/rev/a849fcfdead5
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•