- From: Boris Zbarsky via GitHub <sysbot+gh@w3.org>
- Date: Sun, 08 Jul 2018 08:27:45 +0000
- To: public-css-archive@w3.org
The point is, the current browser behavior for "content" on ::before and ::after is interoperable across all browsers, has been for well over a decade, and follows the existing and finalized CSS 2.1 spec. If the draft wants to change the spec _and_ make all browsers change behavior then chances are the draft is just flat-out wrong. Now you're correct that this only matters if there is lack of compatibility with existing content, but given how long the current behavior has been implemented in browsers and the existing standards situation, the burden of proof should be on anyone who wants to change the behavior to demonstrate lack of compat problems. -- GitHub Notification of comment by bzbarsky Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2889#issuecomment-403271689 using your GitHub account
Received on Sunday, 8 July 2018 08:27:55 UTC