Skip to content
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.

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

CSS: parse-content accepts <baseline-position> #17818

Merged
merged 1 commit into from Jul 16, 2019

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jul 13, 2019

When parse-content is a <baseline-position> value like
last baseline, align-content is the <baseline-position>
and justify-content is start.

https://drafts.csswg.org/css-align-3/#place-content

We add WPTs for serialization of all the place-*
shorthands.

Bug: 983753
Change-Id: I332c75b631efd29e398ba42985529b664c828b04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1698173
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#677928}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already reviewed downstream.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-1698173 branch 2 times, most recently from 431ca4e to 63fa00b Compare July 14, 2019 10:02
When parse-content is a <baseline-position> value like
last baseline, align-content is the <baseline-position>
and justify-content is start.

https://drafts.csswg.org/css-align-3/#place-content

We add WPTs for serialization of all the place-*
shorthands.

Bug: 983753
Change-Id: I332c75b631efd29e398ba42985529b664c828b04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1698173
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#677928}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants