[buddypress-trac] [BuddyPress Trac] #6825: Warnings after running scsslint build task
buddypress-trac
noreply at wordpress.org
Sat Jan 16 04:10:25 UTC 2016
#6825: Warnings after running scsslint build task
-----------------------------------+------------------
Reporter: henry.wright | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 2.5
Component: Tools - Build Process | Version:
Severity: normal | Resolution:
Keywords: |
-----------------------------------+------------------
Comment (by netweb):
'''PseudoElement'''
I've opened a [https://github.com/brigade/scss-lint/issues/678 SCSS-Lint
issue upstream] to support single colon syntaxes for `PseudoElement`
> ... note that IE8 (and other old browsers that don't understand the
newer :: syntax) will see the double colon pseudo-elements and ignore the
entire ruleset as per the requirements in the CSS 2.1 spec says to do.
>
> ... using SCSS-Lint with WordPress and as IE8 is still a supported
browser by WordPress, WordPress uses single colon `:` syntaxes for pseudo-
elements.
For now disabling the rule in `scss-lint.yml` will suffice:
{{{
PseudoElement:
enabled: false
}}}
'''EmptyLineBetweenBlocks'''
The `EmptyLineBetweenBlocks` lint errors are via
https://github.com/brigade/scss-lint/pull/632:
> This only affects @media and @at-root, which are not control flow. It
seems like `EmptyLineBetweenBlocks` should always expect empty lines
around these.
There is no current way to exclude requiring a new line around `@media` so
updated patch will include this change (which kind of in fact normalizes
existing emtpy lines anyway)
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6825#comment:11>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list