Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 458069

Summary: [csslint] Whitespace after CSS selector body causes parse problems
Product: [ECD] Orion Reporter: Michael Rennie <Michael_Rennie>
Component: ClientAssignee: Michael Rennie <Michael_Rennie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 8.0   
Target Milestone: 8.0   
Hardware: PC   
OS: Mac OS X   
Whiteboard:

Description Michael Rennie CLA 2015-01-21 12:50:04 EST 
Depending on how much whitespace is after each selector body in a CSS file the csslint parser produces the incorrect node ranges.

For example:

.annotationHTML.currentLine {
}
.annotationHTML.matchingSearch {
}

vs. this:

.annotationHTML.currentLine {
}

.annotationHTML.matchingSearch {
}

produces an off-by-one problem for the second selector