Closed
Bug 318128
Opened 19 years ago
Closed 19 years ago
Please decide whether the CSS loader is a service or not
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
People
(Reporter: neil, Assigned: dbaron)
References
()
Details
Attachments
(1 file, 2 obsolete files)
14.06 KB,
patch
|
benjamin
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
Then I can run up a patch to switch the errant consumers.
Comment 1•19 years ago
|
||
It's not a service. We have existing bugs on at least some of the code that uses GetService to get it, iirc.
Reporter | ||
Comment 2•19 years ago
|
||
This changes the four cases found by the query. I converted the code to use NS_NewCSSLoader in the two layout sources. I was worried that something was expecting the CSS loader to outlive the function but it hasn't stopped me from using this patched build to attach the patch so I guess it's not an issue ;-)
Attachment #204501 -
Flags: superreview?(bzbarsky)
Attachment #204501 -
Flags: review?(bzbarsky)
Comment 3•19 years ago
|
||
Won't this lead to some perf impact from all the thrashing? Some of these (document viewer and chrome registry) would likely want CSSLoaders fairly often...
Reporter | ||
Comment 4•19 years ago
|
||
I can cache the CSS loader in the chrome registry if you like (I can't write a patch for toolkit because I don't have a xulrunner tree). Since the stylesheet cache already caches the stylesheets I didn't see the point of caching the CSS loader as well, and the document viewer only requires its CSS loader when the usechromesheets attribute is set, which only applies to the sidebar in Modern. I do see that I could optimize the placement of the loader creation slightly.
Attachment #204534 -
Flags: superreview?(bzbarsky)
Comment 5•19 years ago
|
||
Comment on attachment 204534 [details] [diff] [review] Cache CSS loader? > Since the stylesheet cache already caches the stylesheets I didn't see the > point of caching the CSS loader as well It'd prevent us from creating (quite as many) oodles of CSS loaders at startup... I agree that for the viewer this might be a non-issue.
Attachment #204534 -
Flags: superreview?(bzbarsky) → superreview+
Updated•19 years ago
|
Attachment #204501 -
Flags: superreview?(bzbarsky)
Attachment #204501 -
Flags: superreview-
Attachment #204501 -
Flags: review?(bzbarsky)
Attachment #204501 -
Flags: review-
Reporter | ||
Comment 6•19 years ago
|
||
Attachment #204501 -
Attachment is obsolete: true
Attachment #204534 -
Attachment is obsolete: true
Attachment #205031 -
Flags: superreview?(bzbarsky)
Attachment #205031 -
Flags: review?(benjamin)
Comment 7•19 years ago
|
||
Comment on attachment 205031 [details] [diff] [review] Updated patch Thank you for doing this! sr=bzbarsky
Attachment #205031 -
Flags: superreview?(bzbarsky) → superreview+
Updated•19 years ago
|
Attachment #205031 -
Flags: review?(benjamin) → review+
Reporter | ||
Comment 8•19 years ago
|
||
Fix checked in.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•