Closed
Bug 283047
Opened 20 years ago
Closed 15 years ago
stricter rules for preprocessor usage in css
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
DUPLICATE
of bug 305767
People
(Reporter: annevk, Unassigned)
Details
Not sure if the component/product is correct, but that is trivial to change. As discussed in bug 281645 it is a bit unclear if CSS files (and I assume this applies to other files as well) should be preprocessed. And if they should, why it does not apply to all CSS files. Some CSS files do use it, and others within the same directory (project wide there is more variety) do not. When the guidelines are discussed and set up this bug or its follow-up should provide a patch to make everything consistent. Or at least, make everything according to the specified rules.
Updated•20 years ago
|
Summary: stricter rules for the file preprocessor → stricter rules for preprocessor usage in css
Comment 1•20 years ago
|
||
Reassigning to General to get off my radar...
Assignee: jwalden+fxhelp → firefox
Component: Help Viewer → General
QA Contact: help → general
Updated•18 years ago
|
Assignee: bross2 → nobody
Comment 2•15 years ago
|
||
Bug 305767 replaced the "#" marker by "%" for css files.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•