W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2020

Re: [csswg-drafts] [css-syntax-3] Input stream processing can calculate wrong encoding (#4126)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 06 May 2020 00:02:35 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-624368184-1588723354-sysbot+gh@w3.org>

Agenda+ to get WG confirmation that leaving the Syntax spec as it is (matching the sniffing behavior of HTML) is fine.

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

Received on Wednesday, 6 May 2020 00:02:36 UTC

This message: [ Message body ]
Next message: Tab Atkins Jr. via GitHub: "Re: [csswg-drafts] [selectors-4] [css-syntax-3] Does the U+0000 → U+FFFD rule apply to selector parsing? (#4927)"
Previous message: Chris Lilley via GitHub: "Re: [csswg-drafts] [css-color-4] Do gradients/animations using lab/lch colors interpolate in the Lab colorspace? (#4647)"
In reply to: [ message archived in another list or period ]
Next in thread: CSS Meeting Bot via GitHub: "Re: [csswg-drafts] [css-syntax-3] Input stream processing can calculate wrong encoding (#4126)"
Maybe reply: CSS Meeting Bot via GitHub: "Re: [csswg-drafts] [css-syntax-3] Input stream processing can calculate wrong encoding (#4126)"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:06 UTC