W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2019

[csswg-drafts] [css-syntax] 4.3.11. Consume a name? (#3589)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Feb 2019 23:02:55 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-405907422-1549062174-sysbot+gh@w3.org>
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-syntax] 4.3.11. Consume a name? ==
(migrated from the mailing list)

**Hiep, H.A. said:**
> The specification reads:
> 
> ``Repeatedly consume the next input code point from the stream:''
> 
> And whenever the code point does not match the two clauses mentioned below,
> 
> ``anything else
>     Return result.''
> 
> I believe that this description wrong. The current code point should be reconsumed, before returning the result, and preventing that a non-matching symbol from the input stream is eaten by the algorithm. A counter-example:
> 
> #ident{
> }
> 
> would then first consume the "#", which triggers the `Consume a name'-algorithm. It then continues with the `name code point'-path, all the way up to "{". Here it returns result, while "{" is still consumed.
> 
> If I may suggest a better wording, it would be:
> 
> ``anything else
>     Reconsume the current input code point and return result.''
> 
> See:
> http://www.w3.org/TR/css-syntax-3/#reconsume-the-current-input-code-point
> http://www.w3.org/TR/css-syntax-3/#consume-a-name

-------------

**Tab Atkins said:**
> The /TR version is, as usual, out of date.  This issue has been fixed
> in the Editors Draft at
> <https://drafts.csswg.org/css-syntax/#consume-name> for quite a while.
> ^_^

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3589 using your GitHub account
Received on Friday, 1 February 2019 23:02:57 UTC

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