Closed Bug 79313 Opened 24 years ago Closed 24 years ago

editorShell ApplyStyleSheet does not work for jar resource

Categories

(Core :: DOM: Editor, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: pwilson, Assigned: rubydoo123)

Details

When I run an XUL app from unzipped files the following line works correctly: editorShell.ApplyStyleSheet("chrome://xulapp/content/JSsyntax.css"); If I zip these same file into a jar and install the application I get the following error from the above line: Error: [Exception... "Component returned failure code: 0x80520006 [nsIEditorShell.ApplyStyleSheet]" nsresult: "0x80520006 (<unknown>)" location: "JS frame :: chrome://xulapp/content/JSEditor.js :: anonymous :: line 41" data: no] Source File: chrome://xulapp/content/JSEditor.js Line: 41
hrm, so is this a bug in Editor or Chrome? [Chrome?]
Component: Browser-General → Editor
Summary: editorShell ApplyStyleSheet does not woork for jar resource → editorShell ApplyStyleSheet does not work for jar resource
I don't see how it can be an editor bug. We are using very standard APIs for loading CSS files. It seems to me it shouldn't matter whether it's in a jar or not, but I'm not the one who would know that.
updating component and owner
Assignee: asa → trudelle
Status: UNCONFIRMED → NEW
Component: Editor → XP Toolkit/Widgets: XUL
Ever confirmed: true
QA Contact: doronr → jrgm
Um, this may not be it, but your style sheet filename is mixed case. A mismatch won't matter on a win32 filesystem, but will matter when looked up in a jar file. So, if the filename is 'jsstatus.css' it won't be found, and hence, won't be applied. If not, need a full, preferably simple, example. I think Editor should actually own this, at least as far as pointing out where the editor shell fails and why.
Assignee: trudelle → beppe
Component: XP Toolkit/Widgets: XUL → Editor
QA Contact: jrgm → sujay
Er, to be clear, if it's a case mismatch, then this bug is INVALID.
The call to applyStyleSheet in my code does indeed contains a different capitalization than the file name. I was unaware of this feature in jar files. Pilot error.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.