Re: [csswg-drafts] [selectors] webkit-prefixed pseudo-elements are always treated valid in WebKit and Blink from Nadya678 via GitHub on 2018-01-05 (public-css-archive@w3.org from January 2018)

From: Nadya678 via GitHub <sysbot+gh@w3.org>
Date: Fri, 05 Jan 2018 21:06:52 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-355665533-1515186410-sysbot+gh@w3.org>

Then we now can only drink a ![flask](https://user-images.githubusercontent.com/31185239/34628194-d1d63cd6-f263-11e7-9b04-f2268779f9f5.jpg) for this madness? 

Please check Jigsaw validator. The -webkit- styles are treated AS WARNING but :-webkit-pseudoclasses and ::-webkit-pseudoelements are treated as ERRORS. 

The ![flask](https://user-images.githubusercontent.com/31185239/34628194-d1d63cd6-f263-11e7-9b04-f2268779f9f5.jpg) shall be drunk by wenbmasters that wrote bugly code without validation of the site. Goody!!!

If WebKit starts to accept //comments and <!--comments in CSS, the other browsers also should? I can write 100 webpages with these constructions or with construction for EDGE to show the page correctly only in EDGE.  


-- 
GitHub Notification of comment by Nadya678
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2156#issuecomment-355665533 using your GitHub account

Received on Friday, 5 January 2018 21:06:57 UTC