- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Jun 2022 13:46:57 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-gcpm-3] Incorrect `element()` as `newValues` for `content` property == GCPM 3 defines [`element()` as `newValues`](https://drafts.csswg.org/css-gcpm-3/#element-syntax) for the [`content` property](https://drafts.csswg.org/css-content-3/#content-property). I believe `element()` is ambiguous because it can be interpreted as a function component value whose name is `element` with no argument. A terminal or non-terminal must be defined between angled brackets, per the [CSS value definition syntax](https://drafts.csswg.org/css-values-4/#component-types), ie. `<element()>`. Please forgive me to not create a separate issue for the following... `content` is defined as `normal | none | [<content-replacement> | <content-list>] [/ [<string> | <counter>]+]?` and both `<content-replacement>` and `<content-list>` includes `<image>`. I think `<content-replacement>` can be removed. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7351 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 June 2022 13:46:58 UTC