[css-gcpm-3] Incorrect `element()` as `newValues` for `content` property

[cdoublev]

GCPM 3 defines element() as newValues for the 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, 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.

[faceless2]

This has come up before, see #2657. The distinction between the two is valuable, specifically:

• content-replacement is a single image - it makes the node a replaced-content node.
• content-list is a list of one or more items, possibly including images. The node contains replaced content, but is not replaced itself.

The linked-to issue above gives an example.

[cdoublev]

Got it, thanks.

[cdoublev]

The same problem exists for running() defined as a new value for the position property. But waiting for an eventual resolution to retire GCPM as a Note status.