The patch updates the Marionette client and all Marionette unit
tests to make use of the new `Create Window` command as much as
possible.
Depends on D13663
Differential Revision: https://phabricator.services.mozilla.com/D13664
--HG--
extra : moz-landing-system : lando
By default PollPromise has to behave similar to a normal Promise
and wait forever until it gets resolved or rejected.
Depends on D13662
Differential Revision: https://phabricator.services.mozilla.com/D15907
--HG--
extra : moz-landing-system : lando
To be closer to other test harnesses which are using executeSoon()
to run a task on the main thread, this patch adds the same
method to Marionette's sync module.
Differential Revision: https://phabricator.services.mozilla.com/D13659
--HG--
extra : moz-landing-system : lando
Previously we assumed that the path for the lsan_suppressions.txt file was the same as the prefs path,
which is correct in CI but wrong for local builds. This adds a --lsan-dir command line argument and sets
it in mach to the correct value for local builds and uses the prefs directory as a default for backwards
compatibility
Differential Revision: https://phabricator.services.mozilla.com/D16024
--HG--
extra : moz-landing-system : lando
This patch is alarmingly large, but I did not see any leaks in any of
these directories, even with a dozen or so retriggers. We can
whitelist stuff if there are any more intermittents I failed to catch.
Depends on D16090
Differential Revision: https://phabricator.services.mozilla.com/D16091
--HG--
extra : moz-landing-system : lando
I saw this intermittent leak, but it was only a single string.
Depends on D16089
Differential Revision: https://phabricator.services.mozilla.com/D16090
--HG--
extra : moz-landing-system : lando
To detect when the window got minimized usally "visibilitychange" events
are fired to the content window. The "WebDriver:MinimizeWindow" command
has to wait for those.
Depends on D16096
Differential Revision: https://phabricator.services.mozilla.com/D16098
--HG--
extra : moz-landing-system : lando
This commit adds a test that implementations can anchor to node that's inside
of a fragmented node.
Differential Revision: https://phabricator.services.mozilla.com/D16275
--HG--
extra : rebase_source : 3a8a8a3eddbced312adc8739f7f1e6aaeb7c6632
extra : intermediate-source : fbc14e9852b1b4dbfb729be6a5be5c86ce235c98
extra : source : 0726bf91da593f75563d2592c59228c3585290a1
As per the following spec change:
4ec1deb76a
Spec issue:
https://github.com/w3c/csswg-drafts/issues/3193
Of the added test cases, only the last one, "Returns reversed animations yet to
reach their active phase" fails without this code change. The others pass
because the animation is finished at that point but I added them for consistency
with the previous tests.
Differential Revision: https://phabricator.services.mozilla.com/D16001
--HG--
extra : moz-landing-system : lando
The patch updates the Marionette client and all Marionette unit
tests to make use of the new `Create Window` command as much as
possible.
Depends on D13663
Differential Revision: https://phabricator.services.mozilla.com/D13664
--HG--
extra : moz-landing-system : lando
By default PollPromise has to behave similar to a normal Promise
and wait forever until it gets resolved or rejected.
Depends on D13662
Differential Revision: https://phabricator.services.mozilla.com/D15907
--HG--
extra : moz-landing-system : lando
To be closer to other test harnesses which are using executeSoon()
to run a task on the main thread, this patch adds the same
method to Marionette's sync module.
Differential Revision: https://phabricator.services.mozilla.com/D13659
--HG--
extra : moz-landing-system : lando
We assumed that this method returned a logger and the fact that it
doesn't means we end up initialising logging a second time with the
default settings rather than the user overrides.
Differential Revision: https://phabricator.services.mozilla.com/D16057
--HG--
extra : moz-landing-system : lando
I believe that changes to 'overflow-anchor' should invalidate the current
scroll anchor. This isn't in the spec, but there's an issue open for it [1].
[1] https://github.com/w3c/csswg-drafts/issues/3494
Differential Revision: https://phabricator.services.mozilla.com/D16273
--HG--
extra : source : 04e2132249ace0a85fb274022949c7cfc5131fe2
extra : amend_source : 01ee5bfd2085dfce5887512a7ddc4668b955f30b
extra : intermediate-source : af4895c87d712e5151146e2fd61c249fb52c355b
We currently perform anchor adjustment in three spots:
1. If the target of RestyleManager::RecomputePosition is in a scroll anchor chain
2. If the reflow root is in a scroll anchor chain
3. In nsHTMLScrollFrame::DidReflow, for itself
It looks like it's possible for a scroll anchor container to be adjusted by (1)
and (2 or 3) in the same PresShell flush.
This should be okay, except that we consume mSuppressAnchorAdjustment when
performing an adjustment, and this can lead us to miss the second time that
we perform adjustments in a PresShell flush.
This commit reworks how we run anchor adjustments so that we collect all
scroll anchor containers that should be adjusted, and only perform the
adjustments once.
Differential Revision: https://phabricator.services.mozilla.com/D16407
--HG--
extra : source : cbdbd08379d99f9d55f756c57d728c28331be5da
This commit adds two tests around anchor selection.
The first tests that 'position: sticky' is an invalid subtree, which is new to
the spec. The second tests that implementations respect 'overflow-anchor' on
the table element, and don't get confused with the boxes generated by tables.
Differential Revision: https://phabricator.services.mozilla.com/D16274
--HG--
extra : rebase_source : 3c2e74a5765d3409a57aa892fe20aa208c5c0e84
extra : intermediate-source : 55addc12904b79f7300e47da96b1d33780a4cbfb
extra : source : 306393539feb1a3391c3a03baaee43e7058bc44a
The only visible change from this change is that telemetry will be
discontinuous. The owners for the relevant telemetry probes have
reviewed this and indicated that this discontinuity is OK.
The WebDriver:TakeScreenshot command relied on the document element's
clientWidth/clientHeight, but should according to the WebDriver
specification use the viewport's dimensions.
Thanks-to: JinaJita <jitajina@gmail.com>
The WebDriver:TakeScreenshot command relied on the document element's
clientWidth/clientHeight, but should according to the WebDriver
specification use the viewport's dimensions.
Thanks-to: JinaJita <jitajina@gmail.com>
All that is really required for this ticket is to invoke |mach android
archive-geckoview| after |mach package| in the right place.
But it's actively unhelpful to have this magic in mozharness --
especially since the documentation in `locales.rst` is subtly
incorrect (the environment variables and Make variables don't quite
work as written). So this commit adds a Mach command to do the actual
work and replaces most of the mozharness magic with that command.
Since the l10n Make targets check out the l10n HG repositories
locally, this basically Just Works without the mozharness checkout
steps when developing locally.
Differential Revision: https://phabricator.services.mozilla.com/D12455
--HG--
extra : moz-landing-system : lando
Not all tests are passing with the initial implementation. Most are due to
differences between Gecko and Blink with regards to ScrollTop, ScrollLeft in
documents with writing-mode: vertical-rl. Some are due to issues in our anchor
node selection algorithm remaining.
Differential Revision: https://phabricator.services.mozilla.com/D13275
--HG--
extra : rebase_source : 0e23fe91ddb62c24709fc73c007069c9c1f10e90
extra : source : 950bf6ad1ef2ee42c0dcbdc102f1828b68329992
Some of these tests were failing on try but passing locally because of viewport
size differences. This commit expands some spacing to ensure the tests are fully
scrollable on most screen sizes.
Differential Revision: https://phabricator.services.mozilla.com/D13274
--HG--
extra : rebase_source : 309f0a754d5ea40e9227dd682bbf8841b099939c
extra : source : b4cb2cbebdb6a099f64e477ec434701d39d4816d
Not all tests are passing with the initial implementation. Most are due to
differences between Gecko and Blink with regards to ScrollTop, ScrollLeft in
documents with writing-mode: vertical-rl. Some are due to issues in our anchor
node selection algorithm remaining.
Differential Revision: https://phabricator.services.mozilla.com/D13275
--HG--
extra : rebase_source : 4280a352ba1a2cf45c6734a75b6b343ef30d415a
extra : histedit_source : 75e5f5a7ef0b32e19b74515d00885eb88af99699
Some of these tests were failing on try but passing locally because of viewport
size differences. This commit expands some spacing to ensure the tests are fully
scrollable on most screen sizes.
Differential Revision: https://phabricator.services.mozilla.com/D13274
--HG--
extra : rebase_source : c9bacfda973acdb699e8ace905e2ea320381ce29
extra : histedit_source : 7802a4c24dad2da083783d6ae68bfa7723f951e6
Using the "Switch To Window" command to check if a user prompt is open
doesn't work because that command doesn't raise a "unexpected alert open"
error. To fix that the "Close Window" command can be used for.
Differential Revision: https://phabricator.services.mozilla.com/D15816
--HG--
extra : moz-landing-system : lando
This patch implements InputType.inputType which is declared by Input Events.
The attribute has already been implemented by Chrome and Safari. Chrome
implements Input Events Level 1, but Safari implements Input Events Level 2.
Difference between them is only whether it supports "insertFromComposition",
"deleteByComposition" and "deleteCompositionText". This patch makes the
level switchable with pref and takes Level 1 by default because Level 2 is
still unstable around event order with composition events.
For reducing string copy cost at dispatching "input" event, this patch
makes EditorInternalInputEvent store valid input-type as enum class,
EditorInputType and resolves it to string value when
dom::InputEvent::GetInputType() is called. Note that the reason why
this patch names the enum class as EditorInputType is, there is InputType
enum class already for avoiding conflict the name, this appends "Editor"
prefix because "input" and "beforeinput" events are fired only when an
editor has focus.
Differential Revision: https://phabricator.services.mozilla.com/D14128
--HG--
extra : moz-landing-system : lando
The WPT for InputEvent.inputType of each execCommand runs all tests in a
test function. Therefore, even if there is an unexpected result, it won't
test other part. Additionally, it tests execCommand's result of the DOM
tree in the contenteditable so that it's not useful for checking
InputEvent.inputType for now.
Therefore, this patch makes the test returns error for each result of
each call of execCommand.
Additionally, it sets contenteditable attribute to a <p> element which cannot
store other block elements like <ul>, <ol>, <div>, etc. Therefore, some of
the execCommand won't work on Gecko since Gecko's editor does not create
invalid child elements as far as possible. Therefore, this patch makes it
a <div> element.
And also adding "insertHorizontalRule", "backColor", "foreColor",
"hilightColor", "fontName", "createLink", "unlink". inputType values for
those commands are defined by current spec. So, if they'd be changed,
we could detect it quickly.
Differential Revision: https://phabricator.services.mozilla.com/D14123
--HG--
extra : moz-landing-system : lando
This is a first step to share LengthOrPercentage representation between Rust and
Gecko.
We need to preserve whether the value came from a calc() expression, for now at
least, since we do different things depending on whether we're calc or not right
now. See https://github.com/w3c/csswg-drafts/issues/3482 and dependent bugs for
example.
That means that the gecko conversion code needs to handle calc() in a bit of an
awkward way until I change it to not be needed (patches for that incoming in the
next few weeks I hope).
I need to add a hack to exclude other things from the PartialEq implementation
because the new conversion code is less lossy than the old one, and we relied on
the lousiness in AnimationValue comparison (in order to start transitions and
such, in [1] for example).
I expect to remove that manual PartialEq implementation as soon as I'm done with
the conversion.
The less lossy conversion does fix a few serialization bugs for animation values
though, like not loosing 0% values in calc() when interpolating lengths and
percentages, see the two modified tests:
* property-types.js
* test_animation_properties.html
Differential Revision: https://phabricator.services.mozilla.com/D15793
--HG--
extra : moz-landing-system : lando
This converts the tabmodalprompt binding to a class, to be constructed along side with the element
by TabModalPromptBox.
TabModalPromptBox will keep the instances in a map and pass it to the callers, instead of the element.
The tests and callers can access the class instance by passing the element reference to the map.
Differential Revision: https://phabricator.services.mozilla.com/D15505
--HG--
rename : toolkit/components/prompts/content/tabprompts.xml => toolkit/components/prompts/content/tabprompts.jsm
extra : moz-landing-system : lando
As decided during the last TPAC meeting the window rect commands
should not return the window state.
Differential Revision: https://phabricator.services.mozilla.com/D15681
--HG--
extra : moz-landing-system : lando
As decided during the last TPAC meeting the window rect commands
should not return the window state.
Differential Revision: https://phabricator.services.mozilla.com/D15681
--HG--
extra : moz-landing-system : lando
Marionette recently had changes made to its window maximisation algorithm
that lets us re-enable this test. It tests that session.window.maximize()
does not hang when the window is already maximised.
Differential Revision: https://phabricator.services.mozilla.com/D15582
--HG--
extra : moz-landing-system : lando
By stopping to use the scriptTimeout parameter with the
WebDriver:ExecuteScript and WebDriver:ExecuteAsyncScript commands
in the Marionette Python client, we can remove it from the server.
Differential Revision: https://phabricator.services.mozilla.com/D15583
--HG--
extra : moz-landing-system : lando
This isn't a supported behaviour and may be responsible for the observed intermittents.
Differential Revision: https://phabricator.services.mozilla.com/D14959
--HG--
extra : moz-landing-system : lando
Before this change, testing/gtest had 19 errors. These errors have been resolved.
Bug 1506611 - Fixed flake8 errors in testing/gtest
Differential Revision: https://phabricator.services.mozilla.com/D15074
--HG--
extra : moz-landing-system : lando
We were using more primitive methods before to support python 2.4, but
that's obviously no longer required.
Differential Revision: https://phabricator.services.mozilla.com/D15539
--HG--
extra : moz-landing-system : lando
In CreateColumnSpanSiblings(), aInitialBlock can be a DetailsFrame.
Therefore, when creating a non-column-span wrapper, we cannot assume
it's always a block frame. We need to use CreateContinuingFrame to
ensure the correct type of continuation is created.
Differential Revision: https://phabricator.services.mozilla.com/D15134
--HG--
extra : moz-landing-system : lando
The width doesn't matter for the tests. It's to fit the 600x600 window
to prevent scrollbar from appearing.
Differential Revision: https://phabricator.services.mozilla.com/D15219
--HG--
extra : moz-landing-system : lando
Rap-P treeherder group for Raptor power tests.
Emit separate PERFHERDER_DATA for power in addition to the performance measurements.
Use magic --host HOST_IP value to have framework load host ip from environment
variable HOST_IP.
As of bug 1513157, minidump_stackwalk is not installed in the test
docker images, so it needs to be downloaded.
Differential Revision: https://phabricator.services.mozilla.com/D14644
--HG--
extra : moz-landing-system : lando
These calls have to happen in the parent process to have any effect. I
experimented with making ServiceWorkerCleanUp.jsm do the remoting itself but
that didn't turn out to be worth the effort and it turns out all of the uses
are currently in the parent process anyway.
Differential Revision: https://phabricator.services.mozilla.com/D15160
--HG--
extra : moz-landing-system : lando
I should have added this test back in bug 590039 and bug 600428, but I didn't.
Differential Revision: https://phabricator.services.mozilla.com/D14827
--HG--
extra : moz-landing-system : lando
This removes the script_timeouts keyword argument from
Marionette#execute_script and #execute_async_script as it is not
compatible with the semantic meaning associated with null in WebDriver.
The script timeout duration for the session can instead be set
using Marionette#timeouts#script.
Depends on D13993
Differential Revision: https://phabricator.services.mozilla.com/D13994
--HG--
extra : moz-landing-system : lando
If a ColumnSetWrapperFrame already has column-span children,
ColumnSetWrapperFrame::GetContentInsertionFrame() will return itself to
let WipeContainingBlock() aware this is the case to reframe.
To make this work, we need to move the reframe condition prior to check
NS_FRAME_HAS_MULTI_COLUMN_ANCESTOR bit because the top level
ColumnSetWrapperFrame never has NS_FRAME_HAS_MULTI_COLUMN_ANCESTOR bit
set.
Differential Revision: https://phabricator.services.mozilla.com/D14819
--HG--
extra : moz-landing-system : lando
Mitmproxy alternate-server-replay returns last found request ignoring match algorithm
Differential Revision: https://phabricator.services.mozilla.com/D13408
--HG--
extra : moz-landing-system : lando
Add some tests to make sure we clamp the interpolated result with
negative easing function on circle(), ellipse(), and inset().
Depends on D14654
Differential Revision: https://phabricator.services.mozilla.com/D14655
--HG--
extra : moz-landing-system : lando
This also updates some existing annotations to collapse lines with
webrender and not-webrender clauses.
Differential Revision: https://phabricator.services.mozilla.com/D14933
--HG--
extra : moz-landing-system : lando
When passed the `--verbose` flag, `mach xpcshell-test` already prints the
current directory, environment variables, and command used for the test.
However, it prints them in Python syntax. This seems like a good thing to do, as
it's a clear indication of what the test is actually doing. But if one wants to
reproduce a problem by running the xpcshell command directly, it's an
error-prone pain to convert from Python lists of strings to the Bourne shell
syntax.
Fortunately, the Python 2.7 `pipes` module has a function, `pipes.quote`, which
produces properly quoted Unix shell commands, ready to be copied and pasted into
one's terminal.
Unfortunately, the xpcshell tests still clean up the $obj/temp/xpc-plugins-FOO
directory, so this still isn't quite ready to go.
Differential Revision: https://phabricator.services.mozilla.com/D10392
--HG--
extra : moz-landing-system : lando
We should let block-size/min-block-size/max-block-size accept keywords as the
initial value, just like width in vertical writing mode or height in horizontal
writing mode.
Depends on D7536
Differential Revision: https://phabricator.services.mozilla.com/D14320
--HG--
extra : moz-landing-system : lando
Support unprefixed min-content and max-content and treat the prefixed
version as aliases for
1. width, min-width, max-width if inline-axis is horizontal, and
2. height, min-height, max-height if inline-axis is vertical, and
3. inline-size, min-inline-size, max-inline-size, and
4. flex-basis.
Besides, update the test cases to use unprefixed max-content and
min-content.
Depends on D7535
Differential Revision: https://phabricator.services.mozilla.com/D7536
--HG--
extra : moz-landing-system : lando
Before this change, testing/awsy had 94 errors and testing/geckodriver had 17. The errors have been resolved
Differential Revision: https://phabricator.services.mozilla.com/D14712
--HG--
extra : moz-landing-system : lando
Bug 1506163 fixed only part of the issue. There are more types of frames
such as table, grid, flex, etc. that create their own block formatting
context.
Instead of propagating NS_FRAME_HAS_MULTI_COLUMN_ANCESTOR to the
children, we explicit carry the bit over to block and inline frames by
checking that their parent doesn't suppress column-span descendants.
Also, remove the unused "onload" from <body> in the tests.
Differential Revision: https://phabricator.services.mozilla.com/D13597
--HG--
extra : moz-landing-system : lando
1-line fix to hero element timing: the performance entry would show up as 'undefined' in profiles because the variable was defined later.
Differential Revision: https://phabricator.services.mozilla.com/D14746
--HG--
extra : moz-landing-system : lando
This simplifies things all around, and gets rid of one more unnecessary
component registration.
--HG--
rename : toolkit/components/extensions/extension-process-script.js => toolkit/components/extensions/ExtensionProcessScript.jsm
extra : rebase_source : 7ceb6ada0730f8241bbd5ddbd889a320da22b1b1
Previously we'd omit it since it was merely an explicit way of requesting the
default behavior. But the spec has changed such that it's not necessarily
equivalent to the default anymore:
https://drafts.csswg.org/css-align/#overflow-values
(Technically the behaviors are probably still equivalent in our implementation,
pending bug 1451380, but we don't have to publicize that via our
serialization.)
Differential Revision: https://phabricator.services.mozilla.com/D14599
--HG--
extra : moz-landing-system : lando
We have to shim global.self for some tests that we want to run in the shell (see part 3).
Differential Revision: https://phabricator.services.mozilla.com/D14315
--HG--
extra : moz-landing-system : lando
We don't support byte streams, transform streams, writable streams, or piping
yet, but we will, and in the meantime our own meta files disable those tests
for us.
Differential Revision: https://phabricator.services.mozilla.com/D14314
--HG--
extra : moz-landing-system : lando
There is no point running any of these, as we have no support whatsoever for
these features currently.
Differential Revision: https://phabricator.services.mozilla.com/D14481
--HG--
extra : moz-landing-system : lando
The main style of <table> is set on the inner TableFrame, not the outer
TableWrapperFrame. Thus, we fail to spot the table as a column-span kid
in nsCSSFrameConstructor::ConstructionBlock().
Differential Revision: https://phabricator.services.mozilla.com/D13957
--HG--
extra : moz-landing-system : lando
Because mozcrash is stateful we can't check for crashes and then later
log them; we need to do everything in one shot. Therefore remove the
check_for_crashes call, rename log_crash to check_crash and make it
return a boolean indicating whether any crashes occured, as well as
handling the logging.
Differential Revision: https://phabricator.services.mozilla.com/D14437
--HG--
extra : moz-landing-system : lando
The functions needed to build the autocomplete request are moved
to the serviceContainer so it can be called from everywhere in
the code, and not only from the JsTerm.
Differential Revision: https://phabricator.services.mozilla.com/D12939
--HG--
extra : moz-landing-system : lando
The functions needed to build the autocomplete request are moved
to the serviceContainer so it can be called from everywhere in
the code, and not only from the JsTerm.
Differential Revision: https://phabricator.services.mozilla.com/D12939
--HG--
extra : moz-landing-system : lando
The keys in the test_paths dict contain the name of the suite e.g. web-platform-tests-testharness, so specify these
keys rather than the generic web-platform-tests key
Differential Revision: https://phabricator.services.mozilla.com/D14284
--HG--
extra : moz-landing-system : lando
We have a few places where C++ calls ChromeUtils::Import directly.
I fixed these to pass the target object directly instead of an empty Optional<>.
Differential Revision: https://phabricator.services.mozilla.com/D14180
--HG--
extra : moz-landing-system : lando
There are multiple fixes contained in this patch:
- fixes for Android/mobile support
- adding extra strings to the ftl file that were never defined before, and previously the ID was just printed to the page
- update test_l10n.py to not rely on about:support anymore
- changing Troubleshoot.jsm to return and ID and args for the strings that should be displayed, so it is compatible with the Fluent API
- misc. fixes so strings that are not localized don't go through the Fluent codepath
Differential Revision: https://phabricator.services.mozilla.com/D15437
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsAttempt to monitor memory from userspace
It is suspected that Taskcluster jobs sometimes fail due to OOM. It is
hard to know what exactly happens if the kernel OOM killer kicks in.
This change attempts to use a user-space solution: earlyoom.
There are two benefits of earlyoom:
1. Logging: we can log the memory usage periodically and the actions
taken by earlyoom when the system is low on memory.
2. Recovery: we can teach earlyoom to prefer to kill browser processes
and avoid python processes (wpt) so that the runner has a chance to
recover (marking the test as CRASH and carrying on).
--
wpt-commits: 02621fd7b68d71f2b27c493ea81d5687643a1e0b
wpt-pr: 14290
Automatic update from web-platform-testsMove EventTiming tests to WPT Try 3
This CL moves the tests in http/tests/event-timing to external/wpt/event-timing.
The slow image is change from php based to python based. The click is now
handled by test driver. and setTimeout is replaced with step_timeout.
Bug: 841224, 908187, 907948, 907949
Change-Id: Ia6359878666cfb96645aa3b7cd7736ce9df97683
Reviewed-on: https://chromium-review.googlesource.com/c/1352617
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612214}
--
wpt-commits: a2e7e014f92c8daf98fb5915b39b9c013c543904
wpt-pr: 14285
Automatic update from web-platform-testsRemove browserName from default Chrome capabilities
The configuration for Chrome currently sends 'browserName' capability
to ChromeDriver by default. This is unnecessary, and causes errors in
several test cases in webdriver/tests/new_session, whenever a test case
wants to set a different browserName.
--
wpt-commits: 04d65b39f4f66d238f0329740ef658fafb446cf5
wpt-pr: 14283
Automatic update from web-platform-testsMove back resources/ustom-elements-helpers.js into custom-elements/resources/custom-elements-helpers.js after darsh7807 (#14295)
This file has no business being in the top-level resources directory.
--
wpt-commits: 32886e656c654b8b69b6767dd2a43dd25aec0fc5
wpt-pr: 14295
--HG--
rename : testing/web-platform/tests/resources/custom-elements-helpers.js => testing/web-platform/tests/custom-elements/resources/custom-elements-helpers.js
Automatic update from web-platform-testsMedia Capabilities: implement response side of Encrypted Media.
This is adding an DecodingInfo class that carries key system access
information back and create a MediaKeySystemAccess.
This implementation in //media/blink is a stub that is meant to only
pass WPT tests at the moment.
Bug: 907909
Change-Id: I3bac0087ca3051defb8b47d10fffdb6052814ae9
Reviewed-on: https://chromium-review.googlesource.com/c/1348733
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611917}
--
wpt-commits: 38ba0516aac49af3e3cd971038266393aa0e107e
wpt-pr: 14289
Automatic update from web-platform-tests
Media Capabilities: implement Blink shell of encrypted media support.
This is adding the interface changes, the code checking for corectedness,
does type conversion and checks for the edge cases mentioned in spec.
This is also adding WPT.
Bug: 907909
Change-Id: Ieebe5b25202a403e50a09576ac283690c0f0ba55
Reviewed-on: https://chromium-review.googlesource.com/c/1348972
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611871}
--
wpt-commits: 7268cc55c89de22afe2823f20aa05b8cab6a66bd
wpt-pr: 14216
Automatic update from web-platform-tests
Revert "Align resource timing buffer full processing to spec PR 168 (reland)"
This reverts commit 6dd060768d1c1183e0d29e422a2213f106d98299.
Reason for revert: suspect causing WebRtcDisableEncryptionFlagBrowserTest.VerifyEncryption to be flaky (FindIt's report)
BUG:chromium:909704
Original change's description:
> Align resource timing buffer full processing to spec PR 168 (reland)
>
> This change implements the processing model from PR 168[1], when
> it comes to setResourceTimingBufferSize(), clearResourceTimings()
> and the firing of the resourcetimingbufferfull event.
>
> This is a reland of
> https://chromium-review.googlesource.com/c/chromium/src/+/1345269
> (but with nicer tests).
>
> [1] https://github.com/w3c/resource-timing/pull/168
>
> Change-Id: I10431bfda7f79b484c7ee5c608bb8a360d905339
> Bug: 908181, 908414
> Reviewed-on: https://chromium-review.googlesource.com/c/1350950
> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
> Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#611174}
TBR=npm@chromium.org,yoavweiss@chromium.org
Change-Id: Ia4bf26c6be1e7c4ae35b904bac25fe031f854604
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 908181, 908414
Reviewed-on: https://chromium-review.googlesource.com/c/1354123
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#611722}
--
wpt-commits: ec13cf1ca3abf13ae1004003e791fd9937be0b49
wpt-pr: 14282
Automatic update from web-platform-tests
Add javascript navigations interop tests
https://github.com/w3c/webappsec-csp/issues/322 raises an interop issue
It appears the issue itself has been fixed since but I've added these
tests regardless to ensure there is no regression.
Bug: 694525
Change-Id: Icb5502e228b3a96c176cbe23d5b4ce9c5c8640ab
Reviewed-on: https://chromium-review.googlesource.com/c/1348054
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611643}
--
wpt-commits: a82d43808d79ecd0074a4623fd69e3a7bb16c188
wpt-pr: 14192
Automatic update from web-platform-tests
Added srcdoc iframe inheritance test
Added a test for behavior around srcdoc iframes CSP inheritance.
This tests the current specified behavior of always inheriting the
parent CSP for srcdoc iframes.
Bug: 694525
Change-Id: I049ef8c5a9e75c052dc2767ea2d523f54cca497f
Reviewed-on: https://chromium-review.googlesource.com/c/1350889
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611638}
--
wpt-commits: ea0386308c52ade6f0c3f0ee6192cb201386e6d8
wpt-pr: 14233
Automatic update from web-platform-tests
[css] Switch part attribute to a DOMTokenList
Adds tests for manipulating it via the attribute.
Renames PartNames() to Part() to match with part(), the API wrapper.
This uses the same IDL as classList.
Bug: 805271
Change-Id: I9715df48478510029f5d985124e46111c41cffc3
Reviewed-on: https://chromium-review.googlesource.com/c/1333014
Commit-Queue: Fergal Daly <fergal@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611570}
--
wpt-commits: 66710fe6fe1fccc5a4b096da62f3585452dd060c
wpt-pr: 14099