This reestablishes the separtion between wptserve and the rest of web-platform-tests.
It moves the parts of the configuration that are specific to wpt out into the
serve.Config class. It also removes the default.config.json file and just puts
the default configuration directly into the code since there it is able to use
things like runtime paths without difficulty.
MozReview-Commit-ID: FXAClJ8JJof
--HG--
rename : testing/web-platform/tests/tools/sslutils/__init__.py => testing/web-platform/tests/tools/wptserve/wptserve/sslutils/__init__.py
rename : testing/web-platform/tests/tools/sslutils/pregenerated.py => testing/web-platform/tests/tools/wptserve/wptserve/sslutils/pregenerated.py
Automatic update from web-platform-testsFile API: lastModifiedDate has been obsolete for a while
--
wpt-commits: 95127fa5adb1d9953899561c152c518c552e4ed0
wpt-pr: 10821
Automatic update from web-platform-testsHook up logging for websocket server
Use warning as the default level to avoid large amounts of debug spew.
--
wpt-commits: f4dfd5fb5f8dda5ba6974c791d153d968edf0aa3
wpt-pr: 10804
Automatic update from web-platform-testsImprove color use in background-clip-content-box-001.html. (#10814)
Originally submitted as <https://github.com/w3c/web-platform-tests/pull/6226>.
Some additional changes by Ms2ger.
--
wpt-commits: b5befcbe4803b7de1a758142a675a1eae60c1bac
wpt-pr: 10814
Automatic update from web-platform-testsReset writing mode for media controls.
Use horizontal-tb on UA stylesheet to make sure the controls look the
same in all writing modes.
Bug: 839142
Change-Id: I7c84afb4f1eef2cf741196b6a8639845aa72066c
Reviewed-on: https://chromium-review.googlesource.com/1041025
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555670}
--
wpt-commits: 7a7d2e13deccb4d68a084446f837410b0cd909f9
wpt-pr: 10809
Automatic update from web-platform-testsFix timing allow check algorithm for service workers
This CL uses the OriginalURLViaServiceWorker() in the timing allow check
algorithm if the response WasFetchedViaServiceWorker(). This way, if a
service worker changes a same origin request to become cross origin,
then the timing allow check algorithm will still fail.
resource-timing-worker.js is changed so it avoids an empty Response,
which is an odd case in terms of same origin checks.
Bug: 837275
Change-Id: I7e497a6fcc2ee14244121b915ca5f5cceded417a
Reviewed-on: https://chromium-review.googlesource.com/1038229
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555476}
--
wpt-commits: 7e9e0aed09557bf971cdea5fabe8872aeed3e0f3
wpt-pr: 10745
Automatic update from web-platform-testsMerge pull request #10446 from w3c/ffs-descriptor
test the @font-face font feature settings descriptor (property already tested)
--
wpt-commits: f9924ae9ab71b715af273e50a9f7256bff8140e4
wpt-pr: 10446
Automatic update from web-platform-testsHTML: document.open() and the document's encoding
For https://github.com/whatwg/html/pull/3661.
--
wpt-commits: f7fd9fa9515a8fe6f0de3c0da08aad1a077784e5
wpt-pr: 10756
Automatic update from web-platform-tests[KeyboardLock] Ensure API is called from a top-level browsing context
This change adds some checks to the keyboard lock API to ensure it was
called from within a supported context, otherwise it now rejects the
promise.
BUG=680809
Change-Id: I3d127422c640d16e43c22adb14755b65eb2cdc6a
Reviewed-on: https://chromium-review.googlesource.com/1038888
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555417}
--
wpt-commits: 90e225b4f5b37986c06f29bd305b0291a30e4867
wpt-pr: 10753
Automatic update from web-platform-testsFix typo in documentation of SourceFile.content_is_css_visual(). (#10786)
--
wpt-commits: a253aa374f4b9cb0ca05bd6c37143774fa725f96
wpt-pr: 10786
Automatic update from web-platform-testsMerge pull request #10625 from vfalconi/add_flexbox_first-letter_test
CSS-Flexbox: Add test for first-letter
--
wpt-commits: a6fdca312f0774eda1fcf6c524bc2de47941ede9
wpt-pr: 10625
Automatic update from web-platform-tests[css-grid] Subtract scrollbar in ComputeReplacedLogicalHeightUsing()
In LayoutBox::ComputeReplacedLogicalHeightUsing() we were using
the OverrideContentLogicalHeight() plus scrollbar height,
that was wrong and we should subtract the scrollbar too.
This caused issues to resolve the percentage heights on grid item
replaced children, if the grid item has a scrollbar.
To fix the issue we just need to follow the suggestion in the TODO
and use OverrideContentLogicalHeight() directly.
This was the last place using OverrideContentAndScrollbarLogicalHeight()
so we can get rid of it. The patch removes that method together with
OverrideContentAndScrollbarLogicalWidth() that was no longer used.
BUG=837141
TEST=external/wpt/css/css-grid/grid-items/percentage-size-replaced-subitems-001.html
Change-Id: I28cf6e65c21e6314808c4430515f06c07d4a739e
Reviewed-on: https://chromium-review.googlesource.com/1035003
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#554834}
--
wpt-commits: 538eedafb15733c6113b44998170a6bbdae7518b
wpt-pr: 10713
Automatic update from web-platform-testsCleanup CSSOM View interfaces test
The CSSOM View interfaces test added the Geometry IDL as untested, but it is never needed (removing it does not affect test results). Removing it means that less IDL needs to be parsed, speeding up the test.
The test also adds Document as an object twice, and refers to the CSSOM spec instead of the CSSOM View spec. This change fixes both of these issues as well.
--
wpt-commits: dce95ec0d867129a8f4810330b473eca3e515cea
wpt-pr: 10715
Automatic update from web-platform-testsFetch: fix and cleanup api/cors
cors-multiple-origins went against the specification and required support for multiple origins listed in Access-Control-Allow-Origin.
--
wpt-commits: e47396d5c643c6a0bc4782045a8cc77233df3514
wpt-pr: 10708
Automatic update from web-platform-tests[LayoutNG] Improve handling of adjoining floats.
A float always needs to be positioned by its block parent, so passing
them around to children, parents or siblings really shouldn't be
necessary (and it *was* somewhat confusing, since nobody but the direct
float parent is allowed to touch them anyway, apart from placing them
into temporary exclusion spaces). The main reason for passing them
around like that, was for other blocks to determine, based on the list
of floats being empty or not, the need for relayout once the BFC offset
was resolved.
Instead, confine the list of unpositioned floats to the block parent of
those floats, and introduce the concept of adjoining float types (none,
left, right, both). Adjoining floats occur when the BFC offset is
unknown, meaning that their position may be affected by the current
layout algorithm.
Adjoining float types will now be the thing that's both input to and
output from the layout algorithms. Having something other than "none"
means that a block's BFC offset is unknown, but that doesn't
automatically mean that we have to abort and re-layout if the BFC offset
gets resolved. If the "floats BFC offset" is known, for instance, those
adjoining floats may be positioned right away. Still we need to know
about them (positioned or not), to get clearance correct.
We're going to need to treat adjoining floats specially when applying
clearance. Will deal with that in a later CL. For now, we just keep
track of the adjoining float types, so that the clearance machinery can
tell that there are floats there that may not yet be positioned. That
used to be taken care of the list of unpositioned floats, but, as
previously stated, adjoining floats are special, and we need to know
about them, whether they are positioned or not. This is a preparatory CL
for that.
Each time we add an unpositioned float, we need to update the types of
adjoining floats, so that these can be returned from the algorithm if
necessary. Whether they end up being positioned right away or not isn't
relevant. Adjoining is adjoining.
Note that we don't have to #include the header file for unpositioned
floats as much as before now, but I'll clean that up in a follow-up CL,
because it turned out that there were quite a few translation units that
got stuff for free via that header file, instead of explicitly including
what they need.
Had to rewrite how we deal with floats in HandleNewFormattingContext()
and LayoutNewFormattingContext(), since those depended on a list of all
preceding unpositioned floats to place them into a temporary exclusion
space, to figure out whether to let the child's margin be adjoining with
the current margin strut or not. Instead of using a temporary exclusion
space, we now position floats via the regular mechanisms, and initially
assume that the child's margin is going to be adjoining. This means that
we have to abort and roll back if there are preceding unpositioned
floats. This is no different from how we lay out regular blocks, though.
What *is* different is that if it turns out that the child's margin has
to be separated from the strut, we'll have to abort and roll back
once *again* (but only once).
The algorithms now need to keep track of whether they need to abort if
the BFC offset *changes*, rather than if it is *resolved*. We only allow
the offset to resolve and optionally change *once* afterwards, though.
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Ie527d659213049f180ebedc764e1d7f4926a5876
Reviewed-on: https://chromium-review.googlesource.com/1030191
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555314}
--
wpt-commits: 39563cf141605683bb8d76abb74eaa0c764d6c65
wpt-pr: 10725
Automatic update from web-platform-testsDisable kerning in wpt/css/CSS2/floats-clear/floats-143.xht
This patch fixes wpt/css/CSS2/floats-clear/floats-143.xht not
to rely on kerning table.
This test has "PA" and "SS" in two different floats, assuming
either of the below is true:
a. The font does not have a kerning pair between "A" and "S".
b. UA applies kerning across two different floats.
This patch changes this test not to rely on these conditions.
This fix is another test fix needed for CL:1022191.
Change-Id: I78ea57b619fd08a9d671d507ebbb005b556fc183
Reviewed-on: https://chromium-review.googlesource.com/1036825
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555066}
--
wpt-commits: fe5aaaf49f48a36dd468213e00734725109d7b90
wpt-pr: 10737
Alexander Surkov
Bogdan Tara
Dorel Luca
Ted Mielczarek
Aki Sasaki
Raul Gurzau
Christoph Kerschbaumer
Samuel Thibault
Yuri Khan
Jason Duell
Coroiu Cristina
Ryan VanderMeulen
Ben Kelly
moz-wptsync-bot
James Graham
Guido Urdaneta
Anne van Kesteren
Josh Matthews
Ms2ger
Simon Pieters
Rune Lillesveen
Nicolas Pena
Chris Lilley
Mustaq Ahmed
Joe Downing
Greg Whitworth
Manuel Rego Casasnovas
Chris Nardi
Morten Stenshorne
Eric Willigers
Koji Ishii