Open Bug 61711 Opened 24 years ago Updated 2 years ago

Backend support for loading images after page is loaded

Categories

(Core :: Layout, enhancement)

enhancement

Tracking

()

Future

People

(Reporter: timeless, Unassigned)

References

Details

In order to implement a Show Images toolbar button, there needs to be a method that can be called to load document images. I think the following values as a parameter should also be accepted refetchImages loadMissingImages loadSiteImages [this does not include blocked images] loadNonsiteImages [offsite images that are not blocked] loadBlockedImages [this overrides the users preference not to load certain images] loadImages=loadSiteImages+loadNonsiteImages loadAllImages=loadMissingImages+loadImages SuppressUserPrompt [there is a pref to ask the user before loading each image, this flag would override that preference] Similarly, it would be helpful if there was a status to indicate if the page knows of any images that aren't loaded [and to which category they belong].
Reassigning to layout. The embedding people would quite like to see a more fine-grain method to enable image loading as well.
Assignee: adamlock → clayton
Component: Embedding: Docshell → Layout
QA Contact: adamlock → petersen
Reassigning to Buster.
Assignee: clayton → buster
where do you want this "load document images" method? what do you want the result to be? adam, what priority does this have for the embedding team? thanks.
Status: NEW → ASSIGNED
Build reassigning Buster's bugs to Marc.
Assignee: buster → attinasi
Status: ASSIGNED → NEW
Target Milestone: --- → Future
*** Bug 148593 has been marked as a duplicate of this bug. ***
*** Bug 206415 has been marked as a duplicate of this bug. ***
.
Assignee: attinasi → other
Priority: P3 → --
QA Contact: petersen → ian
->Misc Code
Assignee: other → misc
Component: Layout → Layout: Misc Code
QA Contact: ian → nobody
This is doable completely via chrome JS, no? Grab the images from the DOM, QI to nsIImageLoadingContent, kick off the loads. Make sure that your content policy impl doesn't block them. So in my opinion this bug is mis-assigned.
*** Bug 239743 has been marked as a duplicate of this bug. ***
Assignee: layout.misc-code → nobody
QA Contact: nobody → layout.misc-code
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.