While using this in conjucntion with PAReview to check some CSS, I've noted that lines containing CSS comments immediately following a closing brace causes Drupal_Sniffs_CSS_ClassDefinitionOpeningBraceSpaceSniff to (incorrectly) return errors, despite a single newline of the correct format being used. I have already confirmed that it is formatted correctly using a hex editor.

I attach a test case that returns the following errors:

--------------------------------------------------------------------------------
FOUND 7 ERROR(S) AFFECTING 7 LINE(S)
--------------------------------------------------------------------------------
7 | ERROR | Expected exactly one new line after opening brace of class
| | definition
12 | ERROR | Expected exactly one new line after opening brace of class
| | definition
18 | ERROR | Expected exactly one new line after opening brace of class
| | definition
25 | ERROR | Expected exactly one new line after opening brace of class
| | definition
30 | ERROR | Expected exactly one new line after opening brace of class
| | definition
35 | ERROR | Expected exactly one new line after opening brace of class
| | definition
40 | ERROR | Expected exactly one new line after opening brace of class
| | definition
--------------------------------------------------------------------------------
CommentFileSizeAuthor
baseline.txt662 bytesalexiswatson

Comments

klausi’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.