- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Sep 2017 16:41:02 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `<hash-token> seems to get type ID for sequence "#-\" followed by EOF`, and agreed to the following resolutions: * `RESOLVED: Fix the check for a valid escape as described in #1821.` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: <hash-token> seems to get type ID for sequence "#-\" followed by EOF<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1821<br> <dael> TabAtkins: Def a bug, needs ahcnage. I won't do details, but if you have a malformed hash token at end of stylesheet it can sometimes report i t's valid even though it can try and escape an EOF.<br> <dael> TabAtkins: If you have a hash token with like a # symbol [missed]<br> <dael> TabAtkins: hash -/end of stylesheet it's [missed] This is a small bug to test if something is a valid escape. I don't check to see if second character is EOF. If I add that it won't have any additional consiquences.<br> <dael> TabAtkins: All bug were extemely minute. It's just that this is not what was intended in the spec.<br> <dael> florian: Go for it.<br> <dael> Rossen_: Any other opinions or concerns on this topic?<br> <dael> Rossen_: If not we can resolve.<br> <dael> Rossen_: obj?<br> <dael> RESOLVED: Fix the check for a valid escape as described in #1821.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1821#issuecomment-332582375 using your GitHub account
Received on Wednesday, 27 September 2017 16:40:52 UTC