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)

defect
Not set
major

Tracking

()

VERIFIED FIXED
mozilla1.9alpha1

People

(Reporter: mossop, Assigned: asqueella)

References

Details

(Keywords: dev-doc-complete, regression)

Attachments

(1 file)

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
Summary: style lines from manifest files no longer applies → style lines from manifest files no longer applied
We shouldn't ship alpha1 with this, IMO.
Assignee: nobody → asqueella
Flags: blocking1.9?
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.
Dave, do you have particular steps to reproduce?  Is a particular extension involved?
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.
Summary: style lines from manifest files no longer applied → style lines from manifest files no longer applied when xul cache disabled
Attached patch patchSplinter Review
Duh.
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)
Component: XRE Startup → XP Toolkit/Widgets: XUL
Flags: first-review?(bzbarsky)
OS: Windows XP → All
Product: Toolkit → Core
Hardware: PC → All
Need to document the change comment 6 describes.
Keywords: dev-doc-needed
QA Contact: xre.startup → xptoolkit.xul
Comment on attachment 246353 [details] [diff] [review]
patch

Makes sense.   r+sr=bzbarsky
Attachment #246353 - Flags: superreview+
Attachment #246353 - Flags: review+
Whiteboard: [checkin needed]
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
Status: RESOLVED → VERIFIED
Whiteboard: [dev-doc-needed for comment 6]
Flags: in-testsuite?
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.
Added the note I think appropriate at http://developer.mozilla.org/en/docs/Chrome_Registration#style
Whiteboard: [dev-doc-needed for comment 6]
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.

Attachment

General

Created:
Updated:
Size: