Closed Bug 139943 Opened 23 years ago Closed 23 years ago

Command line CSS-checking tool

Categories

(Core :: CSS Parsing and Computation, defect, P2)

defect

Tracking

()

VERIFIED FIXED
mozilla1.0

People

(Reporter: dbaron, Assigned: dbaron)

Details

Attachments

(2 files, 1 obsolete file)

I hacked up a little command line CSS-checking tool so that I could do a CSS-check on all the CSS files in the tree with a little 'find' magic. I'd like to get this checked in so I don't lose it. I'll probably need someone to run it over the commercial tree before I land bug 3935.
And, FWIW, I ran this over all CSS files in the tree except for some stuff in layout/html/tests/css/ (I think that's where it was), and filed bug 139942 with the resulting errors.
For the record, to run it, I executed (roughly -- I saved the find results in a file and 'cat'-ed them, actually) the following *one* line in bash: find /builds/.../mozilla/ -name "*.css" | while read FNAME; do ./run-mozilla.sh ./ParseCSS $FNAME >> csserrors; done
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.0
Looks fine: in FileToURI + CallCreateInstance(kStandardURLCID, &url); you might want to check |url| against null, and also check for a null uri in this bit: + nsCOMPtr<nsIURI> uri = FileToURI(filename); + ParseCSSFile(uri);
Comment on attachment 80899 [details] [diff] [review] patch sr=waterson
Attachment #80899 - Flags: superreview+
Comment on attachment 81741 [details] [diff] [review] patch with null checks sr=waterson
Attachment #81741 - Flags: superreview+
Comment on attachment 81741 [details] [diff] [review] patch with null checks r=attinasi
Attachment #81741 - Flags: review+
Comment on attachment 81741 [details] [diff] [review] patch with null checks a=rjesup@wgate.com for branch (and trunk) checkin
Attachment #81741 - Flags: review+ → approval+
Checked in to trunk 2002-04-30 17:03 PDT.
Checked into 1.0 branch, 2002-04-30 19:54 PDT.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
adding fixed1.0.0 keyword (branch resolution). This bug has comments saying it was fixed on the 1.0 branch and a bonsai checkin comment that agrees. To verify the bug has been fixed on the 1.0 branch please replace the fixed1.0.0 keyword with verified1.0.0.
Keywords: fixed1.0.0
David, Could you please verify this on branch and change the keyword from fixed1.0.0 to verifed1.0.0 Thanks !!
as per David's comments in comment # 13, am marking ths bug with keyword verified1.0.0
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: