Skip to content

Conversation

@cdoublev
Copy link
Collaborator

Editorial change replacing explicit optional groups with implicitly optional commas, ie. ... [ , ... ]? with ... , ...?.

I would appreciate this change because parsing against these two syntaxes with the CSS parser I am using, produces two different results (ie. List(..., optionalList(comma, ...)) vs. List(..., comma, ...)), and the second is easier to handle.

I searched for all occurrences with /\[\s*,.+\]\s*\?/. I did not replace the result found in the value definition of copy-into (CSS GCPM 4, not ready for implementation): the whole alternation can be omitted, which seems to be a bug.

Name: copy-into
Value: none | [ [ <custom-ident> <content-level>] [, <custom-ident> <content-level>]* ]?

It should probably be none | [ <custom-ident> <content-level> ]#.

@cdoublev cdoublev force-pushed the optional-group-issue branch from c8d97d4 to c0c43d3 Compare February 21, 2023 13:17
@tabatkins tabatkins merged commit 95ad995 into w3c:main Feb 21, 2023
@tabatkins
Copy link
Member

It should probably be none | [ <custom-ident> <content-level> ]#.

Looks like it, yeah.

@cdoublev cdoublev deleted the optional-group-issue branch February 22, 2023 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants