Automatic update from web-platform-tests[LayoutNG] Use containing block size correctly for abspos.
UpdateOutOfFlowBlockLayout() needs to deal with both the actual
containing block size, as specified by CSS (i.e. the padding box size),
and the border-box size of the object that is the containing block of an
absolutely positioned descendant.
Some light cleanup. We always need the border sizes, so just calculate
them once, unconditionally. Also, there seems no need for a special path
for grid/flex, so I removed it.
Some tests start to pass. All but one are still expected to fail in legacy.
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I85462d76aa9fa3d0105bf079e59f7c2a7a70f117
Reviewed-on: https://chromium-review.googlesource.com/926004
Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537918}
wpt-commits: 58462b6f92aab3eea03ad1ea70923855889ed1e2
wpt-pr: 9589
wpt-commits: 58462b6f92aab3eea03ad1ea70923855889ed1e2
wpt-pr: 9589
Automatic update from web-platform-testsFix WebAudio WPT tests that timeout.
- AudioParam IDL test:
Actually add the IDL to the test. Also removed unused helpers.js.
- MediaElementAudioSourceNode
Fix error because the expected result is mono, so only has one channel.
However, this still fails on bots because there's no audio hardware to
drive the online context.
Bug: 626703
Test: the-audioparam-interface/idl-test.html
Change-Id: I987ad1219da1b6b6ef677f2923416634fa281d5f
Reviewed-on: https://chromium-review.googlesource.com/920261
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537856}
wpt-commits: 0d5ca044187f3e1122661048e84a54e736296198
wpt-pr: 9548
wpt-commits: 0d5ca044187f3e1122661048e84a54e736296198
wpt-pr: 9548
Automatic update from web-platform-testsReadableStream: test piping and queued writes
When the readable stream becomes closed after the first write,
all queued writes should complete before the pipe operation
becomes completed.
This tests the fix for this behavior in the Streams reference
implementation in whatwg/streams#884.
wpt-commits: 4c74a92846442ebb277342c3afe663a2c89955d4
wpt-pr: 9573
wpt-commits: 4c74a92846442ebb277342c3afe663a2c89955d4
wpt-pr: 9573
Automatic update from web-platform-testsUpdate supported font format specifiers
While we do support variations, our format specifier support was not
updated yet. Move all of that to FontCustomPlatformData and add a WPT
test to cover common supported format specifiers.
Test: external/wpt/css/css-fonts/format-specifiers-variations.html
Bug: 804466
Change-Id: I06d7af65cf74e13cec49dc279efb8ffc2b56dda9
Reviewed-on: https://chromium-review.googlesource.com/926007
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537799}
wpt-commits: ee2e2949929d0d371404ec5a3a7bb2873f44b34c
wpt-pr: 9585
wpt-commits: ee2e2949929d0d371404ec5a3a7bb2873f44b34c
wpt-pr: 9585
Automatic update from web-platform-testsFix #8954: update wptrunner requirements
Note this just uses the current stable release of all dependencies
rather than trying to find what the minimum required actually is.
--
Pin wptrunner dependencies
Given it's an application, we should just define the environment we
expect it to run in. This should stop #8954 from regressing, given it
also means we'll be testing against the only possible set of versions
of our dependencies.
wpt-commits: 25f040e64a77219f8e5bde319adc8561d5750823, d936893f3ce7e2530994f8df62799d17cbd56dfb
wpt-pr: 9587
wpt-commits: 25f040e64a77219f8e5bde319adc8561d5750823, d936893f3ce7e2530994f8df62799d17cbd56dfb
wpt-pr: 9587
Automatic update from web-platform-testsOOR-CORS: Port WebCORSPreflightResultCacheItem to network service
This patch reimplements WebCORSPreflightResultCacheItem equivalent
in network service, and share the implementation between the network
service and Blink. The next patch will replace whole
WebCORSPreflightResultCache, and this is the preparation to make
the next patch small.
Bug: 803766
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ifa06967830465236dbe198908062e1952095e55b
Reviewed-on: https://chromium-review.googlesource.com/915543
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537769}
wpt-commits: de9d5d19b70d2d8b39a9e6f9006d0a2fb4f93f53
wpt-pr: 9539
wpt-commits: de9d5d19b70d2d8b39a9e6f9006d0a2fb4f93f53
wpt-pr: 9539
Automatic update from web-platform-testsDelete StylePropertyMap.update()
This is as there is a bug on the spec highlighting the lack of
usefulness of the function: https://github.com/w3c/css-houdini-drafts/issues/656
Bug: 812912
Change-Id: If0b47a4bfa268f55f63e5c80168971164dc63199
Reviewed-on: https://chromium-review.googlesource.com/923501
Commit-Queue: nainar <nainar@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537697}
wpt-commits: 8f3f3d57d537c956eed62f78172325e97f093025
wpt-pr: 9554
wpt-commits: 8f3f3d57d537c956eed62f78172325e97f093025
wpt-pr: 9554
Automatic update from web-platform-tests[css-typed-om] Fix crash involving negative length perspectives.
We were crashing because converting CSSPerspective(-1px) to a CSSValue
returns nullptr. The correct behaviour should be to convert it as
CSSPerspective(calc(-1px)).
Bug: 812620
Change-Id: I5ee70d4fb5eed064bcdad67391c3eb84531144d6
Reviewed-on: https://chromium-review.googlesource.com/924742
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537690}
wpt-commits: 969ae697f67e35fb93c18fa36a57ff605a47256d
wpt-pr: 9567
wpt-commits: 969ae697f67e35fb93c18fa36a57ff605a47256d
wpt-pr: 9567
Automatic update from web-platform-tests[css-typed-om] Handle out-of-range values correctly.
Currently, when we set width to something like -1, we would get an
invalid value for width. According to the spec [1], we should be
wrapping the invalid value in a calc.
This patch wraps invalid values in calc, and changes the test harness
to allow us to test this.
Bug: 545318
Change-Id: I71769e1bc69164c9b7dcf0d2c54ca06b623b5d9e
Reviewed-on: https://chromium-review.googlesource.com/923603
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537685}
wpt-commits: ca39b1ed0fa70e60bfbcbfe5be7e305b0e5c2d20
wpt-pr: 9568
wpt-commits: ca39b1ed0fa70e60bfbcbfe5be7e305b0e5c2d20
wpt-pr: 9568
Automatic update from web-platform-testsFix #7142: Change manifest update process
Earlier, interrupting the manifest-update could end up
causing errors due to the non-atomicity of the process.
Used tempfile to ensure that the file is written correctly.
wpt-commits: 38612167f54c475836c122013756e92b9a8859cc
wpt-pr: 9564
wpt-commits: 38612167f54c475836c122013756e92b9a8859cc
wpt-pr: 9564
Automatic update from web-platform-testsFix wpt/beacon/headers/header-content-type.html slowness
This CL uses ResourceTiming API to speed up the test cases while
avoiding flakiness.
Bug: 779965
Change-Id: I40dc2fae470df296c87c12e432fc7fc7644cc40a
Reviewed-on: https://chromium-review.googlesource.com/923625
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537664}
wpt-commits: b20bddda8e47b046fc6ffccda4897cb81df14102
wpt-pr: 9569
wpt-commits: b20bddda8e47b046fc6ffccda4897cb81df14102
wpt-pr: 9569
Automatic update from web-platform-testsStreams: Tests for abuse of RSBYOBRequest (#9558)
In https://github.com/whatwg/streams/pull/870 it was made impossible to
directly construct a ReadableStreamBYOBRequest. Prior to that it was
possible to violate the state invariants of ReadableByteStreamController
by constructing then using a BYOBRequest directly. Add tests that verify
that it is not possible to construct a ReadableStreamBYOBRequest
directly.
Also add tests that it isn't possible to violate the invariants of
ReadableByteStreamController by re-using a BYOBRequest object.
Also add a test that it isn't possible to keep a BYOBRequest object
valid while releasing the reader lock, as this would also be a way to
violate ReadableByteStreamController's invariants.
Fixeswhatwg/streams#870
wpt-commits: abcd6e9aeb4267511740c45bf8e484b5ca1d95db
wpt-pr: 9558
wpt-commits: abcd6e9aeb4267511740c45bf8e484b5ca1d95db
wpt-pr: 9558
Automatic update from web-platform-testsRefactor tests for sandbox iframes controlled by service worker
This patch is to split sandboxed-iframe-fetch-event.https.html into small
chunks. Each promise_test has smaller number of assertions, so that now we can
see the results for each situation.
Bug: 771815
Change-Id: I75cdd67f92bbb07d6b538b209e1f0819752c3bc8
Reviewed-on: https://chromium-review.googlesource.com/923901
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537606}
wpt-commits: 63a5a6d7c789f004f09e5cbb801b49cfb4426989
wpt-pr: 9556
wpt-commits: 63a5a6d7c789f004f09e5cbb801b49cfb4426989
wpt-pr: 9556
Automatic update from web-platform-testsStop reusing MemoryCache entries for requests with a different source origin.
ResourceFetcher/ResourceLoader now saves the result of the CORS check on
the Resource object. Though the result of the CORS check varies
depending on the source origin, reusing an existing resource fetched by
a different source origin is allowed by mistake.
This patch introduces a logic to prevent MemoryCache entries from being
reused for requests with a different source (requestor) origin by saving
the source origin on the Resource object and comparing that with the new
source origin in Resource::CanReuse(), so that the result of the CORS
check is reused only when the source origin is the same.
An alternative possibly-better approach is to isolate MemoryCache for
different origins by changing the cache identifier to take into account
the source origin of requests. However, to keep the patch small and fix
the issue quickly, this patch just prevents reuse.
Bug: 799477, 809350
Change-Id: Ib96c9e728abe969a53f3d80519118a83392067b4
Reviewed-on: https://chromium-review.googlesource.com/897040
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537580}
wpt-commits: e6bda363d5bc9722b326631c36333d41101c0cb3
wpt-pr: 9536
wpt-commits: e6bda363d5bc9722b326631c36333d41101c0cb3
wpt-pr: 9536
Automatic update from web-platform-testsSet WasFetchedViaServiceWorker for multipart image response
When creating a ResourceResponse from another ResourceResponse,
we need to copy WasFetchedViaServiceWorker and
ResponseTypeViaServiceWorker.
Bug: 737648
Change-Id: I9405738221ef5232e235f9fc400f204b7b558596
Reviewed-on: https://chromium-review.googlesource.com/907012
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537579}
wpt-commits: 75c962d7c542f3a6c6e43bcf18a4bf67a16f86cf
wpt-pr: 9492
wpt-commits: 75c962d7c542f3a6c6e43bcf18a4bf67a16f86cf
wpt-pr: 9492
Automatic update from web-platform-testsReadableStream: Add a test that all queued writes complete on error (#5636)
When a pipe is errored, all currently queued writes should complete
before abort() is called on the underlying sink.
The tests the fix to this behaviour in the Streams reference
implementation in whatwg/streams#884.
wpt-commits: ee7ca4fb8371000d2429a99002d1ad71275d5cde
wpt-pr: 5636
wpt-commits: ee7ca4fb8371000d2429a99002d1ad71275d5cde
wpt-pr: 5636
Automatic update from web-platform-testsFix selection{Start,End} test
Likely due to a copy and paste error, one of the tests that was
meant to cover both selectionStart and selectionEnd only covered
the former. Fix so that it covers both, as it should have from the
start.
wpt-commits: 08dd5d8de9c165badabf9f18b5be21a561d8213a
wpt-pr: 9563
wpt-commits: 08dd5d8de9c165badabf9f18b5be21a561d8213a
wpt-pr: 9563
Automatic update from web-platform-tests[css-layout-api] Implement the guts of the javascript layout runner.
This implements the hooks from the LayoutCustom object into a web
developer defined layout class.
See: https://drafts.css-houdini.org/css-layout-api/#invoke-a-layout-callback
Currently the only useful thing this does to allow the web developer to
return an "auto" block-size, e.g.
registerLayout('foo', class {
*intrinsicSizes() {}
*layout() {
return { autoBlockSize: Math.random() * 100; } // FUN!
}
});
The engine calculates the inline-size, and adjusts the block-size for the
web developer. This is a simplification on the current API as spec'd but
we'll see what the HoudiniTF thinks of this approach.
The other large behaviour change is appropriate "fallback" handling when
something goes wrong. See "fallback" tests.
Bug: 726125
Change-Id: I08cd2e439f4321bd534a4e3f7222fbdb898e1785
Reviewed-on: https://chromium-review.googlesource.com/917423
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537371}
wpt-commits: 1a2e430c6fd35c111ead0d5a0e9afbe874e7c1a2
wpt-pr: 9509
wpt-commits: 1a2e430c6fd35c111ead0d5a0e9afbe874e7c1a2
wpt-pr: 9509
Automatic update from web-platform-testsCorrect integration with Sauce Labs service (#9484)
A recently merged patch centralized configuration values which defined
the domain names available during test execution [1]. That patch was
based on a mistaken assumption regarding the location of that value and
the stage of the test execution at which it would be available.
(Specifically: the value is not present in the environment configuration
object when the "environment extras" are initialized.) This interfered
with the initialization of the "environment" for the Sauce Labs service,
making it impossible to run the tests there.
Defer the retrieval of the environment configuration object to the time
that object's context manager is activated. Update the call sites to
provide the environment configuration at this moment. Also update the
signature of the context manager for the `FontInstaller` "environment
extra" to accept this second parameter.
[1] https://github.com/w3c/web-platform-tests/pull/8614
wpt-commits: e56563d2b1e8bd225bf4c8b4682cbd12beeae1a7
wpt-pr: 9484
wpt-commits: e56563d2b1e8bd225bf4c8b4682cbd12beeae1a7
wpt-pr: 9484
Automatic update from web-platform-testswptrunner: Fix regression in config, interpreter (#9480)
Prior to the application of this patch, the configuration property named
`host` was required to expand the templated JSON file maintained within
the WPT CLI. By removing the property from some browser definitions
without updating that template, commit 1b4f253 introduced failures when
using the `run` sub-command with the effected browsers.
Refactor the logic for generating the configuration to use an in-memory
representation (instead of a file-based template) and conditionally
extend this object with the `host` option for browsers which specify it.
Document the rationale for the browser which requires this
functionality.
wpt-commits: cb2d75fd13182ab3bdd7189dafe2ff7bbf4acd56
wpt-pr: 9480
wpt-commits: cb2d75fd13182ab3bdd7189dafe2ff7bbf4acd56
wpt-pr: 9480
Automatic update from web-platform-testsFix timeouts in WPT AudioParam tests
Replace the tests that are using ScriptProcessor and online contexts
with an offline context and verify all the output values instead of
just one.
This change exposed a couple of issues:
- setTargetAtTime wasn't actually testing setTargetAtTime because a
linearRampToValueAtTime event was called at the same time,
effectively replacing the setTargetAtTime event
- linearRampToValue and exponentialRampToValue tests expose bugs in
Chrome's implementation of these when the event is scheduled in
the past, and there is no preceding event.
Bug: 812285, 626703
Change-Id: Iad3f54dd4373411431c019de44d4c3bad07587ff
Reviewed-on: https://chromium-review.googlesource.com/919151
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537311}
wpt-commits: 81ada4212ece1e2f5c6cc560d6b2f45593679e93
wpt-pr: 9524
wpt-commits: 81ada4212ece1e2f5c6cc560d6b2f45593679e93
wpt-pr: 9524
Automatic update from web-platform-tests[LayoutNG] Don't add zero-width floats to the exclusion space.
The only thing such floats should affect is the block position of
subsequent floats (float rule §5 [1] and clearance). They should not
affect the inline position or inline size of subsequent floats or new
formatting contexts.
The spec isn't actually clear here, although the browsers agree on the
above. Submitted https://github.com/w3c/csswg-drafts/issues/2312
[1] https://www.w3.org/TR/CSS22/visuren.html#float-position
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Ia9e724c8a58fcb017f86f26bdf90394f09414f4e
Reviewed-on: https://chromium-review.googlesource.com/919065
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537274}
wpt-commits: ae06fa4ce5d170f7f34e979b014315e318344ec4
wpt-pr: 9538
wpt-commits: ae06fa4ce5d170f7f34e979b014315e318344ec4
wpt-pr: 9538
Automatic update from web-platform-testsservice worker: Disallow interception for EMBED and OBJECT requests.
This matches the service worker specification and Firefox.
This change itself is probably not enough to skip all EMBED/OBJECT
requests, as some requests get initiated by PepperURLLoaderHost or
MimeHandlerViewContainer.
In implementor concerns:
https://w3c.github.io/ServiceWorker/#implementer-concerns
"Plug-ins should not load via service workers. As plug-ins may get their
security origins from their own urls, the embedding service worker cannot
handle it. For this reason, the Handle Fetch algorithm makes the
potential-navigation-or-subresource request (whose context is either <embed> or
<object>) immediately fallback to the network without dispatching fetch event."
In Handle Fetch:
https://w3c.github.io/ServiceWorker/#handle-fetch
"If request is a potential-navigation-or-subresource request, then:
Return null."
R=kinuko, yhirano
Bug: 771933
Change-Id: Ia04ae8dec8c968de6a73dca088aa88a67b21718a
Reviewed-on: https://chromium-review.googlesource.com/923445
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537245}
wpt-commits: e7607dad61b547e88d1f06a67b1514a3242600ec
wpt-pr: 9555
wpt-commits: e7607dad61b547e88d1f06a67b1514a3242600ec
wpt-pr: 9555
Automatic update from web-platform-tests[css-typed-om] Make StylePropertyMap.set work with calcs.
Currently StylePropertyMap.set doesn't actually work with calcs.
The current way to check if something is, say, a <length> is to
check its CSSStyleValue::Type. However, this doesn't return
the right value for CSSMathValues, whose types may be quite
complicated.
The correct way is to use the CSSNumericValue matching algorthms:
CSSNumericValue::MatchesLength, which also takes into account
CSSMathValues and percent hints.
This patch changes the following to make this work:
- Removed base types from CSSStyleValue::StyleValueType. A base type
like "length" is not really a CSSStyleValue type.
- Removed unused StyleValueTypeToString.
- Changed "Percent" to "Percentage" in CSSProperties.json5 as that's
the correct term.
- Changed make_cssom_types to use the matching algorithms from
CSSNumericValue.
Bug: 545318
Change-Id: I16aa71a4873e9992749f0f52ba641671d109170e
Reviewed-on: https://chromium-review.googlesource.com/901002
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537206}
wpt-commits: b52a7a29208647f209f06ac2e6321987023c196c
wpt-pr: 9535
wpt-commits: b52a7a29208647f209f06ac2e6321987023c196c
wpt-pr: 9535
Automatic update from web-platform-testsAdd initial test set for Accessible Name and Description Computation 1.1 (#9540)
Note that many of the tests are currently named with a number. Those
tests were taken from the original (1.0) test suite created by the
PFWG, and the file names are being preserved to facilitate comparison
of results.
wpt-commits: 2b4cdad36bd267e39565ebaab5982b9b4c482e53
wpt-pr: 9540
wpt-commits: 2b4cdad36bd267e39565ebaab5982b9b4c482e53
wpt-pr: 9540
Automatic update from web-platform-testsAdd tests for the breaking of a multicolumn across columns, including backgrounds and column rules. (#9527)
The *-nobackground-* tests pass in Firefox and Chrome, and the others
pass in Chrome and fail in Firefox due to what I (as a Gecko
implementor) consider to be a Firefox bug. I haven't yet tested other
engines. (Though -nobackground-003 fails in Firefox due to a different
bug, and multicol-breaking-002 doesn't trigger the background-related
Firefox bug.)
Given the level of ambiguity in the multicol spec, I suspect these tests
probably test some things that aren't formally specified. However, I
think that's probably OK for now. One issue that I know of that they
depend on the spec for is w3c/csswg-drafts#2309.
wpt-commits: d04c0d50dbbf7752c27957005a5a659701b781ad
wpt-pr: 9527
wpt-commits: d04c0d50dbbf7752c27957005a5a659701b781ad
wpt-pr: 9527
Automatic update from web-platform-testsReftest for handling important when there is an animation.
This tests https://drafts.csswg.org/css-cascade/#importance
wpt-commits: 5ee47da05ffc366a887788ccdc3f7a0673c35953
wpt-pr: 8689
wpt-commits: 5ee47da05ffc366a887788ccdc3f7a0673c35953
wpt-pr: 8689
Automatic update from web-platform-tests[USVString] Apply USVString into RTCDataChannel.send
Latest spec changed DOMString type of send with USVString.
- https://w3c.github.io/webrtc-pc/#dom-rtcdatachannel
This CL applies USVString type into the RTCDataCchannel.send according to the spec.
Bug: 790860
Change-Id: I3d2e3fef8e6a8cc8ca94a8ae18c2ccb7dcc48016
Reviewed-on: https://chromium-review.googlesource.com/917741
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Commit-Queue: Tommi <tommi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537015}
wpt-commits: 1a3951e267e61077ca566e9872c9abeb229d5751
wpt-pr: 9530
wpt-commits: 1a3951e267e61077ca566e9872c9abeb229d5751
wpt-pr: 9530
Automatic update from web-platform-tests[LayoutNG] Allow zero-width layout opportunities.
Zero-width floats or in-flow block-level objects that establish a new formatting
context may fit beside preceding floats even if there's zero inline space left.
With this change, a couple of tests start passing, but coverage seems a
bit low, so I added a few new ones.
Had to rebaseline fast/text/word-break.html because a zero-width line
may now fit beside a float that takes up all available inline
space. There was a <br clear=all> in the test that used to insert the
line below such a float. We're now compatible with the others (and our
old selves).
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: Iaf394b7039545eea235b2841457f1662e5890ba9
Reviewed-on: https://chromium-review.googlesource.com/916262
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@{#537000}
wpt-commits: e2b2513a9ab764bcec7ccf616a35835d13020e32
wpt-pr: 9503
wpt-commits: e2b2513a9ab764bcec7ccf616a35835d13020e32
wpt-pr: 9503
Automatic update from web-platform-testsUpdating Server creation for localhost (#9202)
In my last change, I missed this line of code. Adding the host parameter and removing the base_path param.
wpt-commits: 09ca41d71aab5d5640804b34e5165f291259f112
wpt-pr: 9202
wpt-commits: 09ca41d71aab5d5640804b34e5165f291259f112
wpt-pr: 9202
Automatic update from web-platform-testsMake WPT webrtc/simplecall.html pass
The test was failing because passing a null ("end of candidates")
candidate to addIceCandidate is not permitted.
Spec link:
https://www.w3.org/TR/webrtc/#dom-rtcpeerconnection-addicecandidatehttps://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addicecandidate
Bug: none
Change-Id: I1f22d27393a482a882ebe9735488d8cb723b6e75
Reviewed-on: https://chromium-review.googlesource.com/918662
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536977}
wpt-commits: 49d8cd27466bcd293f86a5758f21fcd23a97f196
wpt-pr: 9516
wpt-commits: 49d8cd27466bcd293f86a5758f21fcd23a97f196
wpt-pr: 9516
Automatic update from web-platform-tests[css-typed-om] Move inline style map layout tests to WPT.
We used to have some inline style map layout tests for a subset of
properties. This patch moves them to WPT using the new test harness.
Properties added:
- white-space
- vertical-align
- visibility
- z-index
Bug: 774887
Change-Id: Icce056c4d7f56eed3da05834b1c561fddec53a15
Reviewed-on: https://chromium-review.googlesource.com/918203
Commit-Queue: nainar <nainar@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536966}
wpt-commits: e4730a5e002aadca9605485aec9ccb4c122f15de
wpt-pr: 9514
wpt-commits: e4730a5e002aadca9605485aec9ccb4c122f15de
wpt-pr: 9514
