Closed
Bug 162253
Opened 23 years ago
Closed 21 years ago
Move LoadImage() from nsIPresContext to nsIDocument
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: caillon, Assigned: caillon)
References
Details
We should move image loading to content for several reasons:
1. We can kick off background image loading much sooner
(from the CSS Parser as opposed to from Paint)
2. We can then store imgIRequests/imgIContainers in style structs so we can
keep more data about an image (e.g. intrinsic size is needed by
'background-size' and 'background-position')
3. We will fire off an image load once per document as opposed to once per
presContext/presShell (aren't they combined yet?).
Comment 1•22 years ago
|
||
Question, as LoadImage() has deprecated LoadIcon() (see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/resources/icons/iconreference/iconfunctions/loadicon.asp)
should this bug include a global changeover from LoadIcon to LoadImage, or
should I file a seperate bug on this?
Comment 2•22 years ago
|
||
this bug has absolutely nothing to do with any windows-specific APIs, so file a
new bug for that I guess
Comment 3•22 years ago
|
||
Thanks for the quick advice. I'll file a new bug (Enhancement).
Updated•21 years ago
|
Priority: -- → P3
Comment 4•21 years ago
|
||
Now that bug 57607 is fixed, I'm not so sure this is relevant anymore...
LoadImage lives on, since we need one listener per frame with background to
handle invalidation. But given that that's all we use it for, there is no
reason to move it to nsIDocument and definite drawbacks (no reason for
nsDocument to know anything about frames).
| Assignee | ||
Comment 5•21 years ago
|
||
Agreed.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•