8000 Apply the range definition notation by cdoublev · Pull Request #7407 · w3c/csswg-drafts · GitHub
[go: up one dir, main page]
Skip to content

Apply the range definition notation #7407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 8 commits into from
Jun 29, 2022
Merged

Apply the range definition notation #7407

merged 8 commits into from
Jun 29, 2022

Conversation

cdoublev
Copy link
Collaborator
  • apply the range definition notation in property value definitions
  • reference the range definition notation from CSS Syntax and apply the range definition notation in descriptor and rule's prelude value definitions
  • normalize Infinity to ∞ in range notations
  • rewrite <grid-line> with the range definition notation (multiple intervals)
  • add value definition of <mq-boolean> (defined in prose with a range definition)
  • add value definitions of <size> (defined in prose with a range definition) and <extent-keyword> (previously not exported)

I'm not sure that the last two items do not represent a non-substantive change.

Fixes #7400.

8000
@cdoublev cdoublev changed the title Issue 7400 Apply the range definition notation Jun 23, 2022
@svgeesus
Copy link
Contributor

I'm not sure that the last two items do not represent a non-substantive change.

@cdoublev If you have a W3C Account could you link it to your GitHub account? That would save my having to check each PR for substantiveness :)

@svgeesus
Copy link
Contributor

@frivoal @tabatkins @fantasai would prefer your review before accepting

svgeesus
svgeesus requested changes Jun 23, 2022
View reviewed changes
@cdoublev
Copy link
Collaborator Author

I'm not sure that the last two items do not represent a non-substantive change.

@cdoublev If you have a W3C Account could you link it to your GitHub account? That would save my having to check each PR for substantiveness :)

I do not have one. I do not know if creating an account is open to everyone but I do not plan to make PR often.

@cdoublev cdoublev requested a review from svgeesus June 23, 2022 19:32
@w3cbot
Copy link
w3cbot commented Jun 29, 2022

svgeesus marked as non substantive for IPR from ash-nazg.

@svgeesus svgeesus merged commit fa64907 into w3c:main Jun 29, 2022
@cdoublev cdoublev deleted the issue-7400 branch June 30, 2022 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tabatkins tabatkins 77CD Awaiting requested review from tabatkins

@fantasai fantasai Awaiting requested review from fantasai

@frivoal frivoal Awaiting requested review from frivoal

@svgeesus svgeesus Awaiting requested review from svgeesus

1 more reviewer

@karlikowskipatryk711 karlikowskipatryk711 karlikowskipatryk711 approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Apply the range definition notation
5 participants
@cdoublev @svgeesus @w3cbot @tabatkins @karlikowskipatryk711
0