Closed
Bug 328678
Opened 19 years ago
Closed 18 years ago
Xulrunner should include about:plugins support?
Categories
(Toolkit Graveyard :: XULRunner, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozillabugs.philipl, Assigned: benjamin)
References
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
neil
:
first-review+
|
Details | Diff | Splinter Review |
The current xulrunner package does not include plugins.html and plugins.css which are required for about:plugins to work.
It doesn't seem to make much sense to force every embedder to ship copies of these files.
Comment 1•19 years ago
|
||
the about:plugins files should just be shipped as part of the toolkit. plugins.properties is already there, by the way.
With that fix applied, you can just remove browser/extensions/package-fixup
Attachment #217997 -
Flags: first-review?(benjamin)
Assignee | ||
Comment 2•19 years ago
|
||
Comment on attachment 217997 [details] [diff] [review]
Patch
Hrm, I think we probably want to move those files over here.
Comment 3•19 years ago
|
||
which directories would be the most appropriate ?
Assignee | ||
Comment 4•19 years ago
|
||
Neil, this moves plugins.html/css to toolkit/content, ships xpfe from that source location. It also loads the default styling from chrome://global/content/plugins.css, which can be overridden by chrome://global/skin/plugins.css (per bug 305746).
Attachment #217997 -
Attachment is obsolete: true
Attachment #220132 -
Flags: first-review?(neil)
Attachment #217997 -
Flags: first-review?(benjamin)
Comment 5•19 years ago
|
||
Comment on attachment 220132 [details] [diff] [review]
Move plugins.html to toolkit/content, rev. 1
>Index: toolkit/empty-file
>===================================================================
>RCS file: toolkit/empty-file
>diff -N toolkit/empty-file
patch didn't like this ;-)
>\ No newline at end of file
Would be nice to fix this :-)
>+<link rel="stylesheet" type="text/css" href="plugins.css">
Perhaps chrome: doesn't support relative URLs? I had to change this to chrome://global/content/plugins.css to get it to work. [Side note: I seem to remember reading somewhere that @import was preferred to multiple stylesheets but I forget where or why, and it probably doesn't apply here anyway.]
Attachment #220132 -
Flags: first-review?(neil) → first-review+
Comment 6•19 years ago
|
||
(In reply to comment #5)
> >+<link rel="stylesheet" type="text/css" href="plugins.css">
> Perhaps chrome: doesn't support relative URLs?
I'm sure I've used them, but perhaps here it is resolving it against the about: protocol instead?
Assignee | ||
Comment 8•18 years ago
|
||
Fixed on trunk.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•