Closed Bug 1004423 Opened 11 years ago Closed 11 years ago

CSS errors in codemirror.css

Categories

(DevTools :: Source Editor, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Gijs, Unassigned)

References

(Depends on 1 open bug)

Details

Found in bug 971096: [JavaScript Warning: "Expected declaration but found '*'. Skipped to next declaration." {file: "jar:file:///Users/gkruitbosch/dev/builds/obj-x86_64-apple-darwin13.1.0/dist/firefox/Nightly.app/Contents/MacOS/browser/omni.ja!/chrome/browser/content/browser/devtools/codemirror/codemirror.css" line: 175 column: 2 source: " *zoom:1;"}] [JavaScript Warning: "Expected declaration but found '*'. Skipped to next declaration." {file: "jar:file:///Users/gkruitbosch/dev/builds/obj-x86_64-apple-darwin13.1.0/dist/firefox/Nightly.app/Contents/MacOS/browser/omni.ja!/chrome/browser/content/browser/devtools/codemirror/codemirror.css" line: 176 column: 2 source: " *display:inline;"}] [JavaScript Warning: "Unknown property '-moz-border-radius'. Declaration dropped." {file: "jar:file:///Users/gkruitbosch/dev/builds/obj-x86_64-apple-darwin13.1.0/dist/firefox/Nightly.app/Contents/MacOS/browser/omni.ja!/chrome/browser/content/browser/devtools/codemirror/codemirror.css" line: 189 column: 20 source: " -moz-border-radius: 0; -webkit-border-radius: 0; border-radius: 0;"}] [JavaScript Warning: "Expected declaration but found '*'. Skipped to next declaration." {file: "jar:file:///Users/gkruitbosch/dev/builds/obj-x86_64-apple-darwin13.1.0/dist/firefox/Nightly.app/Contents/MacOS/browser/omni.ja!/chrome/browser/content/browser/devtools/codemirror/codemirror.css" line: 260 column: 19 source: ".CodeMirror span { *vertical-align: text-bottom; }"}] I'm guessing that because we're "just" importing code mirror, we don't really want to fix these issues on our side, but I could be wrong. Brian, can you clarify?
Flags: needinfo?(bgrinstead)
Yes, this file is directly imported whenever we upgrade CodeMirror. The lines in question are IE7 hacks and not necessary for us, so they *could* safely be removed with a patch that is applied after upgrade. That said, since that file is never modified except for CM upgrades it is not likely an intended target of the new test in bug 971096 so my feeling is to whitelist it in the test.
Flags: needinfo?(bgrinstead)
Great, thanks!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Depends on: 1221380
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.