Closed
Bug 924878
Opened 11 years ago
Closed 11 years ago
codemirror.css should be in skin, not in content
Categories
(DevTools :: Source Editor, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: alfredkayser, Unassigned)
References
Details
No description provided.
Comment 1•11 years ago
|
||
Please, yes.
Comment 2•11 years ago
|
||
Is this actually really needed? Afaik, nobody ever built themes for Orion.
But I imagine it doesn't cost much to move the files to /themes/shared/.
Comment 3•11 years ago
|
||
Are there any advantages of putting CSS files into /themes/ besides customization? I'd like CodeMirror to not be customizable at least for the initial release and until we flesh out all the kinks.
Flags: needinfo?(alfredkayser)
Comment 4•11 years ago
|
||
(In reply to Anton Kovalyov (:anton) from comment #3)
> Are there any advantages of putting CSS files into /themes/ besides
> customization? I'd like CodeMirror to not be customizable at least for the
> initial release and until we flesh out all the kinks.
Not really. I agree with you, for the moment, we should favor self-contained + maintainable code over customization.
Updated•11 years ago
|
Component: Developer Tools: Scratchpad → Developer Tools: Source Editor
Reporter | ||
Comment 5•11 years ago
|
||
A solution for me would to also include a chrome://browser/skin/devtools/codemirror.css, initially empty, so that themers can at least provide overriding style rules when needed.
Examples where this is needed are my themes, particulary Walnut and Walnut2 where the grey linenumbers column just doesn't fit the Walnut style.
See also the documentation on the CodeMirror site, where one of the key advantages mentioned is the style customizability of CodeMirror.
Right now there is there no way that a theme can adjust styling of the CodeMirror based scratchpad.
Flags: needinfo?(alfredkayser)
Comment 6•11 years ago
|
||
Not in scope for first release but definitely something we can do once we've stabilized. Thanks!
Updated•11 years ago
|
Priority: -- → P3
Reporter | ||
Comment 7•11 years ago
|
||
This is more or less solved by: Bug 895561 - "Edit As HTML" option in the markup view,
by adding the common.css into the codemirror context, so that now themers can apply their own styling on top of the CodeMirror style.
const CM_STYLES = [
+ "chrome://browser/skin/devtools/common.css",
"chrome://browser/content/devtools/codemirror/codemirror.css",
"chrome://browser/content/devtools/codemirror/dialog.css",
"chrome://browser/content/devtools/codemirror/mozilla.css"
];
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•