Take AutoSaveLiveRegisters as an argument, and use that to ensure the registers were saved
--HG--
extra : rebase_source : bb54592bd009afc67aaa0ca9c705ab28f4a45d44
Automatic update from web-platform-testsClean up budget-api idl test (#11445)
Follow up for #9763 now that #10338 is resolved and we have #10381 too.
--
wpt-commits: 7b2cd8b78d938ea8879adc6419f2ea14b6af8bad
wpt-pr: 11445
Automatic update from web-platform-testsUpdate the IDL generated content headers to the content from reffy-reports (#11333)
--
wpt-commits: cdf41ff70d042eb78f461aeb44a5ad383964dbd3
wpt-pr: 11333
Automatic update from web-platform-tests[LayoutNG] Orthogonal flows need available inline size for min/max calculation.
Provide a suitable constraint space when calculating min/max inline
sizes for an orthogonal flow root. ComputeMinMaxSize() in NGBlockNode
typically ended up creating its zero-sized constraint space, which would
typically result in large block sizes (since there'd e.g. only be space
for one word per line).
Set percentage resolution size too, instead of leaving it at 0x0.
Percentages are often unresolvable (i.e. indefinite), in which case we
should of course refrain from resolving them, rather than resolving the
percentage against zero (which we used to do).
Add a DCHECK that we're always provided with a constraint space when
calculating min/max for orthogonal flows, as using the zero-size one
will not produce the correct result.
Bug: 848225
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Ic0aac380b2b733d3a55b25396c89584e4468899d
Reviewed-on: https://chromium-review.googlesource.com/1090845
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565446}
--
wpt-commits: ce22baff58c81ab98f3cbd2ac390e51e755fd9f9
wpt-pr: 11417
Automatic update from web-platform-testsImprove RTCPeerConnection-setRemoteDescription-tracks.https.html tests.
Using async functions and promise_tests instead of then()-chains and
async_tests. This makes them more readable, easier to maintain and
shorter.
Replaced RTCPeerConnection-helper.js function performOffer() with
exchangeOffer()/exchangeAnswer()/exchangeOfferAnswer().
Updated tests that were performing multiple offers to perform a full
offer/answer exchange whenever there were future offers to be made.
Previously it would perform half of an offer/answer cycle before
starting the next offer/answer, which under Unified Plan could lead to
some unexpected failures.
TBR=guidou@chromium.org
Bug: 777617
Change-Id: Ib0305d55af5aef7f49b5418d4ba44ded9c84d5c6
Reviewed-on: https://chromium-review.googlesource.com/1082434
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565234}
--
wpt-commits: fb908f941185aff41514383293f029e21937a87d
wpt-pr: 11301
Automatic update from web-platform-testsAdd selector tests
* Test invalid pseudo-class starting with a valid one
* Test selector in :not() surrounded by spaces
* Test :nth-child used twice in selector
--
wpt-commits: 2436290affb197955acf8aa0115897ce5205dcc4
wpt-pr: 11449
Automatic update from web-platform-testswebdriver: update the webdriver WebIDL and fix test (#9851)
--
wpt-commits: 418538eb1cce3ecd931285db697736aa2066d05c
wpt-pr: 9851
Automatic update from web-platform-tests[idlharness.js] Clean up media-capabilities idl test
Follow up for #11255 which was unable to use add_dependency_idls because of #10338.
--
wpt-commits: c243b3c545f592a1635c770575dc6e20593ee392
wpt-pr: 11442
Automatic update from web-platform-tests[KeyboardMap] Blink module now handles iFrames and multiple calls
This CL adds the following:
- KeyboardMap now requires the caller to be a top-level, secure
browsing context
- Multiple calls to getKeyboardLayout() will now be given the same
promise instead of it being timing dependent (the initial promise
might get overwritten with the old logic)
- Sequential calls to getKeyboardLayout() still get their own promise
- All promise rejections will return a DOM exception (similar to
KeyboardLock)
- I've cleaned up KeyboardLock a bit as well so it has similar
logic/formatting to what I added to KeyboardMap
- Added several tests to KeyboardMap and fixed some failing cases
BUG=832811
Change-Id: I4a03f68c239cff42b8840e9513257384038f04b4
Reviewed-on: https://chromium-review.googlesource.com/1093474
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565833}
--
wpt-commits: 4565dc5875f3841b0884bdfd8ad6b9ad6f4a5944
wpt-pr: 11440
Automatic update from web-platform-testsCreated a test file to directly test the InputFile class in test_request.py, bypassing the server. Found and fixed a bug where passing a file larger than the buffer in InputFile caused the server to crash. Found and fixed a bug where seeking to a position before the current position and calling read() immediately after falsely tried to assert the positions of _buf_pos and _file_pos. Added tests for these bugs. (#11415)
--
wpt-commits: 99eb0f68f85f4d3c44d5c0d80021ed305e2f3613
wpt-pr: 11415
Automatic update from web-platform-testsservice worker: Add long timeout to registration-updateviacache.https.html.
The test is slow because it does a lot of registrations and updates.
Bug: 850842
Change-Id: I5782e4e426e571a604929da7369c8474ffda88e5
TBR: robertma
Reviewed-on: https://chromium-review.googlesource.com/1092958
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565641}
--
wpt-commits: 7bc2ca900c7f5d19040c5a1169d1257cb947459e
wpt-pr: 11434
Automatic update from web-platform-testsAdd the InputDeviceCapabilities IDL file with test (#9755)
--
wpt-commits: 3bc4498426ab48d6e580cb00802bca50e3220317
wpt-pr: 9755
Automatic update from web-platform-tests[idlharness.js] Test exposure set of partial interfaces (#11419)
--
wpt-commits: 24d1bbe29fd1ca3ca18e5154d99058be87cb2f24
wpt-pr: 11419
Automatic update from web-platform-testsAdd ResizeObserver IDL file with test (#9756)
--
wpt-commits: 7684fe30a809662f2af99a78f7c4671195573ce8
wpt-pr: 9756
Automatic update from web-platform-testsAdd css-masking IDL file with test (#9905)
--
wpt-commits: 82a7c8930aae4df57dbd7895b8d3038c095f0790
wpt-pr: 9905
Automatic update from web-platform-testsUpdate the performance-timeline and user-timing IDL files (#9837)
Adds new any.js tests and removes the old ones.
--
wpt-commits: 8cce35711430779302fab1c7f6fda492cd1853a5
wpt-pr: 9837
Automatic update from web-platform-testsCSS Typed OM: Proper types for custom props during iteration.
Currently, you get CSSUnparsedValues when iterating entries on the
.computedStyleMap(), even for properties which are registered with a
type. However, if you do .computedStyleMap().get(...) with a registered
property, you _do_ get the correct type.
This is because ComputedStyleCSSValueMapping::Get properly looks up the
typed values on the ComputedStyle, but ::GetVariables does not; instead it
directly returns the CSSVariableData for everything, regardless of
registrations.
This patch changes the behavior of iteration to use the same code path
as .get(). This ensures that we either create a CSSCustomProperty-
Declaration on the fly for unregistered properties, or we re-use the
existing (and typed) CSSValue for registered properties.
Note: I initially wanted to do a nested iterator thing here, but dropped
it because we would anyway need a temp HashSet to avoid potential
duplicates from the StyleInheritedVariables-root.
Note: One caller of GetVariables() just wants the size. It's possibly a
little overkill to create entire HashMap just to count something,
but I don't want to resolve that here in the same patch.
R=futhark@chromium.org, haraken@chromium.org
Bug: 850072
Change-Id: I64bfb3cc22a377cf956420a9e64d47ca3daac1e2
Reviewed-on: https://chromium-review.googlesource.com/1090848
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565605}
--
wpt-commits: 36bb4d778a8ad51a46e478b6ca98e39cc6f5a8e7
wpt-pr: 11420
Automatic update from web-platform-testsExclude more labels in "Reviewed but still open PRs" (#11378)
--
wpt-commits: 185e07d903b514f8d1a4564923ba63fd4e6c3476
wpt-pr: 11378
Automatic update from web-platform-testsURL: test ' in queries
For https://github.com/whatwg/url/pull/395.
--
wpt-commits: 0e084a927078d434bcc1952a2ab99fb541f2c25d
wpt-pr: 11389
Automatic update from web-platform-testsRevert "WebKit export of https://bugs.webkit.org/show_bug.cgi?id=186127 (#11279)" (#11424)
This reverts commit 57fea798e1e933e1d5291608d9d12da661185bcb.
According to @birtles, Mozilla CI can have several tens of seconds between two
frames while the test assumes only hundreds of milliseconds. So this is likely
to be flacky.
--
wpt-commits: fb6713ed45c4f285fff02db91bf631dd89b84250
wpt-pr: 11424
Automatic update from web-platform-tests[PageLifecycle] Add sendBeacon to the freeze WPT test
navigator.sendBeacon should be allowed during the onfreeze callback,
there was no changes in the code needed to enable it since it is
implemented using fetch-keepalive, that is already allowed.
This CL adds a test to make sure that this does not regress.
Bugi: chromium:838684
Change-Id: I71b628ccce4dfbf1f2bd012c24866cd908f56d30
Reviewed-on: https://chromium-review.googlesource.com/1091638
Reviewed-by: Shubhie Panicker <panicker@chromium.org>
Commit-Queue: Fadi Meawad <fmeawad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565478}
--
wpt-commits: ee048e6c440fb14aa63b96ca8900208cd122cacb
wpt-pr: 11421
Automatic update from web-platform-testsConvert word-wrap to an alias of overflow-wrap
word-wrap was previously defined as its own property in
CSSProperties.json5, but with the same behavior as overflow-wrap.
However, this meant that word-wrap showed up alongside word-wrap in
cssText. This patch converts word-wrap to be an alias of overflow-wrap,
as this will prevent the issue of both properties showing up in cssText
and matches the resolution in
https://github.com/w3c/csswg-drafts/issues/866.
Bug: 679068
Change-Id: I3d415eb1cde9a92dffa2a045ba5fa8b015eeb2d7
Reviewed-on: https://chromium-review.googlesource.com/1073677
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Chris Nardi <cnardi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#565331}
--
wpt-commits: 71aca0a171ce75d1acfc43e1e523f709612addb8
wpt-pr: 11282
