Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Currently sass-lint generates the following warnings on 3 files:
warning Pseudo-elements must start with double colons pseudo-element
These files are:
- sass\base\links\_links.scss
- sass\base\text\_text.scss
- sass\init\clearfix\_clearfix.scss
The W3c specification does recommend using single-colon notation for backwards compatibility:
CSS3 however also still allows for single colon pseudo-elements, for the sake of backwards compatibility, and we would advise that you stick with this syntax for the time being.
https://www.w3.org/community/webed/wiki/Advanced_CSS_selectors#CSS3_pseu...
In order to turn off those warnings you need to add pseudo-element: 0
in the file .sass-lint.yml
Comment | File | Size | Author |
---|---|---|---|
#3 | disable_pseudo_element_check-2751687-11443903.patch | 315 bytes | amourow |
Comments
Comment #2
amourowI have the same issue, and also add the property to my .sass-lint.yml.
here is the patch to the issue
Comment #3
amourowComment #4
ckrinaIn https://www.w3.org/community/webed/wiki/Advanced_CSS_selectors#CSS3_pseu... it says:
It asks to use single colon pseudo-elements for backwards compatibility, and it refers to Internet Explorer 8:. But Drupal 8 & Zen 8.x-7.x/7.x-6.x are not supporting IE8 anymore right?
I would suggest to change the selectors adding the double colon instead of disabling the scss-lint rule.
Comment #5
thanhdo1991 CreditAttribution: thanhdo1991 commentedThe single-colon will support most of the browsers
The double colon will only support safari, chrome
The single-colon is better than double colon.
Should add the property `pseudo-element: 0` to .sass-lint.yml.
Comment #6
andypost