Automatic update from web-platform-tests
[docs] Simplify recommendation for advanced usage
The steps listed in the "Tips & Tricks" section largely summarize the
instructions in the preceeding sections with two exeptions:
1. the recommendation to rebase (which lacks a definition)
2. the warning against modifying the branch following submission (which
conflicts with a prior section)
Remove the steps and expand the recommendation of Pro Git.
--
wpt-commits: 4b93a2e9c9f904265ae755291ca253045adb3f66
wpt-pr: 17369
Automatic update from web-platform-tests
Merge pull request #17292 from gsnedders/ahem-part2b
Add ahem.css to many more tests
--
wpt-commits: daf75e3bc7829fc4de06bff7136009210aafe3e5
wpt-pr: 17292
Automatic update from web-platform-tests
[Navigation Timing] secureConnectionStart should be non-zero
The value of secureConnectionStart should be non-zero for secure
context navigations. It wasn't. This CL makes sure that it is!
Bug: 977519
Change-Id: Ia12e2842bc061e687512f1ed94d02c07f4dd42ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1672068
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671799}
--
wpt-commits: 87e1dabfa2ef2cf1d1946f428d19973b9bb35ddc
wpt-pr: 17438
Automatic update from web-platform-tests
Add more tests for fraction gaps. (#17486)
These tests check the gap parameters from https://mathml-refresh.github.io/mathml-core/#fractions-mfrac
The existing frac-parameters-1 and frac-parameters-2 tests use mspace elements as numerator/denominator so the box returned by getBoundingClientRect() perfectly encloses the visual rendering of these elements.
These versions rely on reftests to check when mtext elements are used as numerator/denominator with a font typo ascent/descent different from the actual glyph's bounding box ascent/descent. In each case, three glyphs are tested (centered, above or below the baseline).
These tests pass on gecko/webkit but currently fail with the chromium-mathml build for glyphs that are not centered on the baseline.
--
wpt-commits: ecc43f56d11b2485f17bf57c0db2031778d3eca9
wpt-pr: 17486
Automatic update from web-platform-tests
Bring XRRay.matrix and XRRay constructors up to spec
Minor update to XRRay.matrix algorithm to recompute internal matrix
if it was detached.
Modification to XRRay's constructors to throw InvalidStateError in
case direction normalization cannot be performed.
Update WPT tests to account for the change.
Bug: 957763
Change-Id: I7e65b660de013badbc2cff249d5a75a5fa75ab96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1671871
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671779}
--
wpt-commits: 766f40ade665477bdc44b5070a5d7cf533748552
wpt-pr: 17462
Automatic update from web-platform-tests
[wpt PR 16992] - Revert "Frame freezing on load.", a=testonly
Automatic update from web-platform-tests
Revert "Frame freezing on load."
This reverts commit 0daefdcf34ba9a8c21ab907b2159c5652169a45b.
Reason for revert:
DCHECK(!GetDocument()->LoadEventStillNeeded());
in local_frame.cc is failing at
https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests%20%28dbg%29
Original change's description:
> Frame freezing on load.
>
> Move load event checks to renderer side so it is consistent with the
> page lifecycle spec. Add additional resource that is slow to load
> to ensure the load event is waited for correctly before freezing.
>
> BUG=907125
>
> Change-Id: I8f45ddffcf3ce88f6244307833325a54e1c2d395
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625464
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Avi Drissman <avi@chromium.org>
> Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662340}
TBR=avi@chromium.org,haraken@chromium.org,dtapuska@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 907125
Change-Id: I4e27e30519359e2a3ef0d2c92a0fc9d88ac78aff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628499
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#663009}
--
wp5At-commits: 138d2e938d493a5c8435025162759c2e34b3b1d1
wpt-pr: 16992
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1554083
gecko-commit: 6b5ce266625e08bf06a40e6fd2b9b419a9f7f3ed
gecko-integration-branch: central
gecko-reviewers: testonly
--
wpt-commits: 87c8ca1b6f9debb046752ca92d6cea7af6e9f17c
wpt-pr: 17463
Automatic update from web-platform-tests
[wpt PR 17233] - Active Processing for ConvolverNode, a=testonly
Automatic update from web-platform-tests
Active Processing for ConvolverNode
The ConvolverNode should output a single channel of silence when it is not
actively processing. Active processing is already supported and just needed
to have the convolver output a single channel of silence when it is
constructed, before anything is connected to it.
Bug: 971389
Change-Id: Icc894cd7ea6dec60a1eccb0fa4a3aea68ac5b51f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1644899
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#668149}
--
wp5At-commits: 6531eab802391a24dabca973cc4329abbeadd896
wpt-pr: 17233
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1558611
gecko-commit: 3b9b543d1c8db5573155dc6ff44e65f871ae6ec9
gecko-integration-branch: central
gecko-reviewers: testonly
--
wpt-commits: 9e43b67f4fec9e0a1ffe2d91a5b4fd0c9b5ad705
wpt-pr: 17461
Automatic update from web-platform-tests
Revert "Insert a generated item after preserved spaces following a forced break"
This reverts commit 6b0ca8ce33e71d570fce11ae6fb5f898ddf053e4.
Reason for revert:
Broke external/wpt/css/css-text/word-break/word-break-break-all-004.html on many Mac bots:
https://ci.chromium.org/p/chromium/builders/ci/Mac10.10%20Tests/44291https://ci.chromium.org/p/chromium/builders/ci/Mac10.11%20Tests/39449https://ci.chromium.org/p/chromium/builders/ci/Mac10.12%20Tests/24278https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests/14909https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Mac10.13%20%28retina%29/16025
Original change's description:
> Insert a generated item after preserved spaces following a forced break
>
> We already had to implement a special logic to deal with leading
> preserved white spaces due some optimizations we have in the line
> breaking code to give always breaking opportunities before spaces.
>
> However, the presence of forced breaks may cause some of the following
> spaces becoming leading preserved spaces in the next line.
>
> This patch applies the same logic we had for such leading spaces at
> the text's first line. It also needs to define additional cases in the
> function that evaluates the need of adding these generated breaking
> opportunity items.
>
> Bug: 976195
> Change-Id: If39e7ba8a535c15d33d6021c6cd04da9590b1131
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1667305
> Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#671656}
TBR=jfernandez@igalia.com,kojii@chromium.org
Change-Id: I418bb0d30fce7f9ac5724f76c0a854bcb070aa5c
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 976195
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674249
Reviewed-by: Dan Beam <dbeam@chromium.org>
Commit-Queue: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671703}
--
wpt-commits: 3d97450f2c48758db3f76f3360ff7c3e4069c320
wpt-pr: 17465
Automatic update from web-platform-tests
Add test checking SharedArrayBuffers are transferred over MessageChannels
SharedArrayBuffers in Chrome don't end up getting passed correctly when
it crosses a document boundary. This is because of the simplistic
Cluster Agent Key implementation. SharedArrayBuffers are currently
passed correctly provided the MessageChannel is all inside the same
document. (a document and itself, or a document and an associated worker).
BUG=798572
Change-Id: I012b2fbdae52ebee7d26034caa996f2e0cf929ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1672777
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671672}
--
wpt-commits: b3418ad6bf7b49e59025e5278e1291587c6fc10e
wpt-pr: 17454
Automatic update from web-platform-tests
Insert a generated item after preserved spaces following a forced break
We already had to implement a special logic to deal with leading
preserved white spaces due some optimizations we have in the line
breaking code to give always breaking opportunities before spaces.
However, the presence of forced breaks may cause some of the following
spaces becoming leading preserved spaces in the next line.
This patch applies the same logic we had for such leading spaces at
the text's first line. It also needs to define additional cases in the
function that evaluates the need of adding these generated breaking
opportunity items.
Bug: 976195
Change-Id: If39e7ba8a535c15d33d6021c6cd04da9590b1131
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1667305
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671656}
--
wpt-commits: 9348328991a301000225e6da1010755eceaf1389
wpt-pr: 17393
Automatic update from web-platform-tests
[docs] Add detail on writing Python handlers (#17386)
Extend the documentation on writing Python handlers to more completely
describe the feature. Introduce a short example to concretely
demonstrate its usage. Apply similar changes to the corresponding
documentation in the `wptserve` directory for parity.
--
wpt-commits: acbefd606a1b9284b96d21a4a332d0202e36d531
wpt-pr: 17386
Automatic update from web-platform-tests
[Azure Pipelines] put parenthesis pack in step names
This reverts drive-by changes for consistency in commit
e75855649360298870a40ed78874bd4ab1470c20, which actually left the step
names inconsistent.
--
wpt-commits: 42ea2f906ab2367dc4403fb5cf8f7d476f9e0e5c
wpt-pr: 17409
Automatic update from web-platform-tests
Improve failing condition of a test (#17452)
So it doesn't time out.
--
wpt-commits: 1f512077ca0998e0af60ff727eea8c8ba5d78491
wpt-pr: 17452
Automatic update from web-platform-tests
Revert "[serve] Make pywebsocket honor log_level config"
This reverts commit 7edf9eabfae3550a4dd2a48625e68b02a734de15.
--
Fix pywebsocket logging properly
The previous attempt (#17124) called pywebsocket._configure_logging,
which had the unwanted side effect of resetting lots of logging setup in
the pywebsocket subprocess (e.g. mozlog configured by wptrunner -- the
log messages produced by pywebsocket lost its structure and became a
simple STDERR text captured by mozlog.capture).
Instead of calling pywebsocket._configure_logging, the original issue
(log level in config.json not honoured by pywebsocket) should be fixed
by setting the log level on the root logger instead, which will set up
all loggers (including those in third-party libraries) correctly. This
is done only on the entry point of `wpt serve` and won't affect
wptrunner which has its own logging setup.
--
wpt-commits: b693b1b954a8828dc5a0c69319e234b9e3b2d76d, 6e7ac6df08e23d9c8e7aa3223f387f71beb39b9c
wpt-pr: 17433
Automatic update from web-platform-tests
Handle null ::first-letter text layout object.
Ideally, UpdateFirstLetterPseudoElement() will remove the ::first-letter
pseudo element from the DOM when there is no text which can contain the
first letter. Hence, we should not end up in a situation where we try to
AttachLayoutTree for the FirstLetterPseudoElement with a null
first_letter_text.
However, the layout tree is different in AttachLayoutTree() than in
UpdateFirstLetterPseudoElement() in the case where there already was a
::first-letter pseudo element, since we detached it right before
AttachLayoutTree. This means we may have different results for
FirstLetterTextLayoutObject() at those two points if the method has
bugs.
Such a bug was found here where a list item marker inside an anonymous
block had an out-of-flow sibling, but we were not able to traverse out
of the anonymous block to find the first letter text.
Add a DCHECK to let us trigger cases where FirstLetterTextLayoutObject()
is buggy, but also add if-tests to make sure we don't crash.
Bug: 977044
Change-Id: Id80f8aad5c04678d64927e7a7ca4d60cdb6a4b8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1672845
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671629}
--
wpt-commits: 53ebe42e282c9cd4c49d8e615b30eee06c2211a0
wpt-pr: 17447
Automatic update from web-platform-tests
[shapedetection] Add some shapedetection tests
Cover following two checkpoints:
- If the ImageBitmapSource is an HTMLVideoElement object whose readyState attribute
is either HAVE_NOTHING or HAVE_METADATA then reject the Promise with a new
DOMException whose name is InvalidStateError.
- If the ImageBitmapSource argument is an HTMLCanvasElement whose bitmap’s origin-clean
flag is false, then reject the Promise with a new DOMException whose name is SecurityError.
spec: https://wicg.github.io/shape-detection-api/#image-sources-for-detection
Change-Id: I0522d0340d3cb0291df6be65dfc1ab99037b30f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1666766
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Cr-Commit-Position: refs/heads/master@{#671578}
--
wpt-commits: ec977dea05df9ce55c03a842ffe05a1bf6ee399a
wpt-pr: 17392
Automatic update from web-platform-tests
[Native File System] Create FileSystemFileWriterImpl to mirror the renderer side
This is the initial cl of the refactor of NativeFileSystemFileHandleImpl to
mirror the split on the renderer side with the handle and the writer as
two separate entities.
It is the initial implementation for FileSystemFileWriterImpl. It includes
only one no-op method for now: close().
This sets the stage for atomic writes as close() will be the explicit
termination of a write, which allows us to do the atomic operation.
Bug: 968550
Change-Id: I0af81efa46789f18c4a8b0bca3ab89c5703b798c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662709
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Auto-Submit: Olivier Yiptong <oyiptong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671539}
--
wpt-commits: 3cb5a99e5521936fb8819de8aaba806050b84184
wpt-pr: 17364
Automatic update from web-platform-tests
Add mandatory capabilities parameter in the body for the webdriver new session command (#17212)
--
wpt-commits: 693543f7296ef79cc4ec534422c5a0bb433992dd
wpt-pr: 17212
Automatic update from web-platform-tests
[css-flexbox] Clamp the cross-size by the min/max size
...when computing the main-axis size of a flex item.
As per this change:
https://drafts.csswg.org/css-flexbox/#change-2018-used-cross-sizeR=dgrogan@chromium.org, eae@chromium.org
Bug: 972576
Change-Id: I11a1ac14e2e0e44e39fcd45d4568874da2dcfce8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1672014
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671485}
--
wpt-commits: cc0f6ffd9998bdc180d3c70354656f438d99f701
wpt-pr: 17434
Automatic update from web-platform-tests
Don't skip fragment clip if there are other clips for composited layers
Composited layer under multicol is still not fully correctly
supported. Currently we don't allow fragmentation of composited layers,
and skip fragment clip for them. However, if there are other clips below
the fragment clip, we should not skip fragment clip to ensure the other
clips are correctly applied. This is still not fully correct (see the
comment in the code for details), but the result is less broken in many
cases. Hopefully we'll fully fix the issue in
CompositeAfterPaint+LayoutNG-box-fragments.
Bug: 976187
Change-Id: Ica9acc71f0d1204d6380f1bcac3e2159631d63e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670413
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671480}
--
wpt-commits: 1c33536fe6e7d2a6a0323bdb849a5a80c33513a6
wpt-pr: 17429
Automatic update from web-platform-tests
[LayoutNG] Fix |ComputeMinMaxSize| not to clear |NeedsLayout|
This patch fixes |ComputeMinMaxSize| not to clear |NeedsLayout|
when all of following conditions are met:
1. Needs |MinMaxSize|
2. Is an orthogonal flow root.
3. Is legacy layout.
4. Change is applied that dirties the layout.
In this case, |NGBlockNode::ComputeMinMaxSize()| calls
|Layout()|, which goes to |RunLegacyLayout()|, which calls
|LayoutObject::LayoutIfNeeded()|. However, its constraint
space is intermediate that it does not update
|CachedLayoutResult|.
Then when laying it out, because |NeedsLayout()| is cleared,
existing out-of-date |CachedLayoutResult| is used.
This patch fixes:
1. Not to pre-layout orthogonal roots if it has
|CachedLayoutResult|.
2. Set |NeedsLayout()| if |RunLegacyLayout()| clears it, but
|CachedLayoutResult| was not updated.
Bug: 976859
Change-Id: Ic2d979a3c4f9479040bfd0e54cf4283b60ed52b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670146
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671460}
--
wpt-commits: 47b08c15495e05fa73e243736742851109198af1
wpt-pr: 17428
Automatic update from web-platform-tests
Remove unused BroadcastChannel in portal-activate-data.html.
It was probably left behind during recent WPT refactoring.
Change-Id: Ia993654248303c56559cb8cf755d11944213048a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1671947
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Auto-Submit: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671414}
--
wpt-commits: 674c9f5b6c076746d8823ee215181b9b471cd1a4
wpt-pr: 17431
Automatic update from web-platform-tests
[docs] Deprecate some requirement flags (#15964)
Reference: https://github.com/web-platform-tests/wpt/issues/5293
Also update the example to use non-deprecated flags.
--
wpt-commits: a56df4a639b5e1c278037d53ce461f66e06c902a
wpt-pr: 15964
Automatic update from web-platform-tests
[docs] Reorganize information on Ahem
WPT maintains a document dedicated to configuring systems to run the
tests. Relocate the instructions on installing Ahem to this document,
and reference them from their original location (an explanation of how
to use the font to author tests).
--
wpt-commits: 49e92561e87e4e1dd7a798dc74f69378b4526878
wpt-pr: 16339
Automatic update from web-platform-tests
[docs] Enable Sphinx's "nit-picky" mode
The `-n` flag to Sphinx is documented as "warn about all missing
references." Enable that flag and correct the missing references which
were previously tolerated.
--
[docs] Incorporate wptserve documentation
While Sphinx is capable of including the contents of files which exist
outside of the documentation root (via the `include` directive), it
interprets such text in the context of the including file. That makes
the mechanism inappropriate for including documentation that references
still other files using relative paths.
To address this, create a symbolic link to the `wptserve` source
directory. Fix or ignore infractions in the newly-incorporated files.
--
wpt-commits: 929bb86fff798cac3b94af7a2549480fac40a84e, a54dccec285341423d3e956bcbdbaac5b0e45ab8
wpt-pr: 17418
Automatic update from web-platform-tests
Worker: Deflake worker-interception.https.html
This is a follow-up CL for
https://chromium-review.googlesource.com/c/chromium/src/+/1657855/10#message-de50523b6c1fc520cf1a7c2edf3033d4e2139103
worker-interception.https.html is flaky on Firefox. It looks like service worker
unregistration is unexpectedly canceled. Each test case doesn't explicitly
terminate (shared) workers, so they may prolong the lifetime of the registration
being unregistered, and the next test case may unexpectedly reuse it. This
results in failures in setup_service_worker().
To fix it, this CL separates service worker scope per test. Note that explicit
worker termination should not work in this case because shared workers are
out-of-process workers and it's not possible to terminate them
deterministically.
Bug: n/a
Change-Id: I16c32d6477c8b1a4d1a246b33a8e21747b4fec66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1663459
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670831}
--
wpt-commits: 8ad6f6a2ebb5b861f17c1b8084b264c71e6b965b
wpt-pr: 17395
Automatic update from web-platform-tests
Optimize cubic bezier solver.
Newton's method requires an accurate guess to get good convergence.
This patch introduces a linear interpolation of a crude spline as a
starting point for the iterative solver. Previously the starting point
t = x was used. The patch also introduces a tighter tolerance for
Newton's method than the fallback, and is justified by Newton's method
having quadratic convergence characteristics. Speed testing indicates
that the solver is roughly 50% faster, since the number of iterations
is typically less even at the higher accuracy requirement.
Bug: 827560
Change-Id: I89e3cc9061823269aabb16697e2d167751aa52b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643973
Reviewed-by: Ian Vollick <vollick@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670995}
--
wpt-commits: dbe15f82985f2e2a978255665f388c7dcdd425b1
wpt-pr: 17349
Automatic update from web-platform-tests
Expect actionsWithKeyPressed.html to fail on Mac
Related to issue #17296. This PR does not fix the underlying issue, but
only unblocks the infrastructure tests on macOS.
--
Expect elementPosition.html to timeout
For Chrome on macOS
--
wpt-commits: 2e5b9fb08c42966831690bd01b9b6410efc479fa, fe2232a673785d77c1b23509c5ae52c325378918
wpt-pr: 17415
Automatic update from web-platform-tests
[Navigation Timing] Replace TAO restrictions with same-origin ones
The NavigationTiming specification changed [1] to replace TAO based opt-in
to get information about unloadStart, unloadEnd and redirectCount with
same origin restrictions.
Our implementation was not aligned with the old spec language, but
isn't aligned with the new one either.
This CL aligns the implementation with the new language.
Change-Id: Ic4f3c7061e7b9a40f960f0bf26ef26823d5fe743
Bug: 977147
[1] https://github.com/w3c/navigation-timing/pull/108
Change-Id: Ic4f3c7061e7b9a40f960f0bf26ef26823d5fe743
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669355
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671229}
--
wpt-commits: 94f51553f1413cf2118b9bf89762bfad16d8a18a
wpt-pr: 17412
Automatic update from web-platform-tests
Service worker: self.serviceWorker (#17285)
* Tests for self.serviceWorker
* Don't need `self`
* Add read only test
* Adding comments & test the object doesn't change
* Swap order
--
wpt-commits: 3725067ef0328c998be2ba93dbaeb0579586fccd
wpt-pr: 17285
Automatic update from web-platform-tests
[webnfc] Remove incorrect tests (#17425)
Per spec https://heycam.github.io/webidl/#es-DOMString,
non string value will be converted to string via `toString()`
method, therefore there's no `TypeError` to be thrown.
--
wpt-commits: 3a00a57af5f449a72f0e1b89dae6f1bd15ad8fcd
wpt-pr: 17425
Automatic update from web-platform-tests
Worker: Remove duplicate service worker interception tests for shared workers
worker-interception.https.html has more test coverage, and is well-formatted.
Bug: n/a
Change-Id: I29640ffa781c1b90b1faa56eab4f771c1a3c0a84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669137
Auto-Submit: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671183}
--
wpt-commits: 982f12dc86098e5b32ffec455520a5eb114c27af
wpt-pr: 17414
Automatic update from web-platform-tests
[docs] Increase strictness of build process (#17401)
Use the `-W` flag to interpret Sphinx warnings as errors, causing the
build to fail in the presence of either. This makes various authoring
mistakes more visible. Perhaps most importantly: it highlights instances
of "orphaned" content.
Fix all details which were previously reported as warnings and thus
permitted.
--
wpt-commits: 9c6304b71c5ee090ebc1eef02ab32b70444d9704
wpt-pr: 17401
Andreea Pavel
moz-wptsync-bot
Mike Pennisi
Luke Bjerring
Sam Sneddon
pyup-bot
Yoav Weiss
Frédéric Wang
Jack Steinberg
Piotr Bialecki
Emil A Eklund
Mugdha Lakhani
Yuki Shiino
Raymond Toy
Dan Beam
Dave Tapuska
Javier Fernandez
Kagami Sascha Rosylight
Philip Jägenstedt
Emilio Cobos Álvarez
Rune Lillesveen
Wanming Lin
Olivier Yiptong
George Roman
Christian Biesinger
Xianzhu Wang
Koji Ishii
Jeremy Roman
autofoolip
Aleksey Shvayka
Hiroki Nakagawa
Kevin Ellis
Robert Ma
Jake Archibald
Nicolás Peña Moreno