Closed
Bug 361432
Opened 18 years ago
Closed 18 years ago
style lines from manifest files no longer applied when xul cache disabled
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
VERIFIED
FIXED
mozilla1.9alpha1
People
(Reporter: mossop, Assigned: asqueella)
References
Details
(Keywords: dev-doc-complete, regression)
Attachments
(1 file)
(deleted),
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
Stylesheets specified as style lines in chrome manifest files rather than as xml pi's are no longer applied to the document.
Regression range is 2006111104 to 2006111204
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=1163246341&maxdate=1163336280
Choosing to blame bug 319654
Reporter | ||
Updated•18 years ago
|
Summary: style lines from manifest files no longer applies → style lines from manifest files no longer applied
Comment 1•18 years ago
|
||
We shouldn't ship alpha1 with this, IMO.
Assignee: nobody → asqueella
Flags: blocking1.9?
Assignee | ||
Comment 2•18 years ago
|
||
I'm looking into it. My debug builds don't have this problem, will have to do a clean debug build and an opt build.
Comment 3•18 years ago
|
||
Dave, do you have particular steps to reproduce? Is a particular extension involved?
Reporter | ||
Comment 4•18 years ago
|
||
Discovered that this only occurs when the xul cache is disabled, so possibly not so much of a problem.
Opening the customize toolbar dialog should demonstrate the problem, most of the items are without their icons.
Reporter | ||
Updated•18 years ago
|
Summary: style lines from manifest files no longer applied → style lines from manifest files no longer applied when xul cache disabled
Assignee | ||
Comment 5•18 years ago
|
||
Duh.
Assignee | ||
Comment 6•18 years ago
|
||
Comment on attachment 246353 [details] [diff] [review]
patch
I meant to do this when I removed the loading code from EndLoad.
The fact that I don't remove the IsChromeURI check does mean that non chrome sheets from the chrome registry won't get loaded, like I guess they used to. I think it's ok, since they were never handled well by the old code (which didn't add them to prototype's sheets).
Attachment #246353 -
Flags: first-review?(bzbarsky)
Updated•18 years ago
|
Component: XRE Startup → XP Toolkit/Widgets: XUL
Flags: first-review?(bzbarsky)
OS: Windows XP → All
Product: Toolkit → Core
Hardware: PC → All
Comment 7•18 years ago
|
||
Need to document the change comment 6 describes.
Keywords: dev-doc-needed
QA Contact: xre.startup → xptoolkit.xul
Comment 8•18 years ago
|
||
Comment on attachment 246353 [details] [diff] [review]
patch
Makes sense. r+sr=bzbarsky
Attachment #246353 -
Flags: superreview+
Attachment #246353 -
Flags: review+
Reporter | ||
Updated•18 years ago
|
Whiteboard: [checkin needed]
Comment 9•18 years ago
|
||
mozilla/content/xul/document/src/nsXULDocument.cpp 1.741
Status: NEW → RESOLVED
Closed: 18 years ago
Flags: blocking1.9?
Resolution: --- → FIXED
Whiteboard: [checkin needed]
Target Milestone: --- → mozilla1.9alpha
Reporter | ||
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•18 years ago
|
Whiteboard: [dev-doc-needed for comment 6]
Assignee | ||
Updated•18 years ago
|
Flags: in-testsuite?
Comment 10•17 years ago
|
||
I'm unclear on what needs documenting here. It looks like a one-line change that fixes a bug; is it something that people actually need specifically documented? I'm just not sure where it would go.
Reporter | ||
Comment 11•17 years ago
|
||
Added the note I think appropriate at http://developer.mozilla.org/en/docs/Chrome_Registration#style
Keywords: dev-doc-needed → dev-doc-complete
Whiteboard: [dev-doc-needed for comment 6]
Assignee | ||
Comment 12•17 years ago
|
||
That's correct.(In reply to comment #11)
> Added the note I think appropriate at
> http://developer.mozilla.org/en/docs/Chrome_Registration#style
>
Thanks, that's the note that should have been added.
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•