b2e0e7f77e
Automatic update from web-platform-tests[LayoutNG] Fix min/max sizes during layout and intrinsic passes. Essentially this boils down to during min/max auto/percent/calc should be treated the same, either being border+padding or infinity. And during layout they should be taken into account. I added some tests which now match FF/Edge (004,005) which LayoutNG matches, but existing layout fails. The primary difference is change by passing kContent into ResolveBlockLength during the ComputeBlockSizeForFragment function. Bug: 635619 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I4e0c171a0e29ea5d85a742d85df001647813c1f3 Reviewed-on: https://chromium-review.googlesource.com/1056291 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#559171} -- wpt-commits: b06b08091c6a39d88957db2389727524258a3140 wpt-pr: 10994 |
||
---|---|---|
.. | ||
compositing | ||
CSS1 | ||
CSS2 | ||
css-align | ||
css-animations | ||
css-backgrounds | ||
css-break | ||
css-cascade | ||
css-color | ||
css-conditional | ||
css-contain | ||
css-content | ||
css-counter-styles | ||
css-display | ||
css-exclusions | ||
css-fill-stroke | ||
css-filter | ||
css-flexbox | ||
css-font-loading | ||
css-fonts | ||
css-gcpm | ||
css-grid | ||
css-images | ||
css-layout-api | ||
css-lists | ||
css-logical | ||
css-masking | ||
css-multicol | ||
css-namespaces | ||
css-overflow | ||
css-page | ||
css-paint-api | ||
css-position | ||
css-properties-values-api | ||
css-pseudo | ||
css-regions | ||
css-rhythm | ||
css-round-display | ||
css-ruby | ||
css-scoping | ||
css-scroll-anchoring | ||
css-scroll-snap | ||
css-shadow-parts | ||
css-shapes | ||
css-sizing | ||
css-speech | ||
css-style-attr | ||
css-syntax | ||
css-tables | ||
css-text | ||
css-text-decor | ||
css-timing | ||
css-transforms | ||
css-transitions | ||
css-typed-om | ||
css-ui | ||
css-values | ||
css-variables | ||
css-writing-modes | ||
cssom | ||
cssom-view | ||
filter-effects | ||
geometry | ||
mediaqueries | ||
motion | ||
reference | ||
selectors | ||
support | ||
tools | ||
vendor-imports/mozilla | ||
WOFF2 | ||
.gitignore | ||
.htaccess | ||
build-css-testsuites.sh | ||
README.md | ||
requirements.txt |
Introduction
This directory contains testsuites for CSS WG specifications, including ones that do not strictly speaking define CSS features, e.g., Geometry Interfaces.
The directories should be named like the specification's shortname, but without any level suffix.
As the test harness relies on the largely undocumented old CSS build system, this directory has a number of test requirements specific to it:
-
support files for a given test must live in an adjacent
support
directory; -
tests must have a
<link rel=help>
pointing to what they are testing; -
for each spec so linked, test filenames must be unique; and
-
support and reference files must have unique filenames within the entire
css
directory.
vendor-imports/ Directory
vendor-imports/ is a legacy directory where third parties historically imported their tests that originate and are maintained in an external repo. Files in this directory should never be modified in this repo, but should go through the vendor's process to be imported here.
Importing Old Branches
Given an old branch in git based against the old csswg-test repository, it can be moved over to the merged repo in one of two ways:
-
(Recommended:) Rebasing on top of web-platform-tests: with the old branch checked out, run
git rebase -Xsubtree=css/ origin/master
(or similar, depending on the name of the upstream remote). -
Merging to web-platform-tests: with web-platform-tests' master branch checked out, run
git merge -Xsubtree=css/ my_shiny_branch
(or similar, depending on the name of your branch).
If you have a branch/bookmark in Mercurial, the process is more complicated:
-
From the Mercurial repo, run
hg export --git -r 'outgoing()' > foo.patch
. This will export all the changeset shown inhg log -r 'outgoing()'
; it's recommended you check this is the right set of changesets before continuing! -
Move to the git repo, and create a new branch based on web-platform-tests' master; e.g.,
git checkout -b hg-import origin/master
(or similar, depending on the name of the upstream remote). -
Download hg-patch-to-git-patch and run
python2 hg-patch-to-git-patch < foo.patch > bar.patch
(wherefoo.patch
is the path to thefoo.patch
you exported above). -
Run
git am --directory=css/ < bar.patch
.