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 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 left a comment

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 Jul 14, 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}
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-1698173 branch from 63fa00b to cd4e493 Jul 16, 2019
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit 00d52d8 into master Jul 16, 2019
15 checks passed
15 checks passed
manifest-build-and-tag manifest-build-and-tag
Details
website-build-and-publish website-build-and-publish
Details
wpt.fyi - chrome[experimental] Chrome results
Details
wpt.fyi - safari[experimental] Safari results
Details
Azure Pipelines Build #20190716.108 succeeded
Details
Azure Pipelines (./wpt test-jobs) ./wpt test-jobs succeeded
Details
Azure Pipelines (affected tests without changes: Safari Technology Preview) affected tests without changes: Safari Technology Preview succeeded
Details
Azure Pipelines (affected tests: Safari Technology Preview) affected tests: Safari Technology Preview succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests) wpt.fyi hook: safari-preview-affected-tests succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests-without-changes) wpt.fyi hook: safari-preview-affected-tests-without-changes succeeded
Details
Taskcluster (pull_request) TaskGroup: success
Details
staging.wpt.fyi - chrome[experimental] Chrome results
Details
staging.wpt.fyi - firefox[experimental] Firefox results
Details
staging.wpt.fyi - safari[experimental] Safari results
Details
wpt.fyi - firefox[experimental] Firefox results
Details
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-1698173 branch Jul 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.