There are few things that are either Fennec-specific or don't work
currently under GeckoView w/ e10s under TestRunnerActivity. Disable
these so we can get some testing going in automation.
This also replaces 'isFennec' with the more correct 'is_fennec'.
Differential Revision: https://phabricator.services.mozilla.com/D19016
--HG--
extra : moz-landing-system : lando
Now that the JsTerm is a React component, we shouldn't
let external consumers have to get the instance in order
to perform some actions on the console input.
We start with the most used actions, setInputValue and getInputValue,
and might extend that in the future.
Differential Revision: https://phabricator.services.mozilla.com/D20685
--HG--
extra : moz-landing-system : lando
Optimizing jars without preloading/reordering data only moves the
jar central directory to the beginning of the file, which, without
preloading information, is not very useful. Let's just stop doing it if
there's not going to be preloading/reordering information at all.
Differential Revision: https://phabricator.services.mozilla.com/D21170
--HG--
extra : moz-landing-system : lando
The HTML formatter now references the correct link and does not produce a 404 error
Differential Revision: https://phabricator.services.mozilla.com/D21207
--HG--
extra : moz-landing-system : lando
The HTML formatter now references the correct link and does not produce a 404 error
Differential Revision: https://phabricator.services.mozilla.com/D21207
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Add .mailmap to map people to their current names
Note that this isn't used by `git log` by default (as of 2.20.1): that
depends on log.mailmap being set to true.
--
Add Tess to .mailmap
--
wpt-commits: 39f54a3dd48b560289e0f455308acf7d32fad043, f8a1bfbe5454352d3f5b58845829968ff212519b
wpt-pr: 15353
Automatic update from web-platform-tests
HTML: noreferer was never a property of hyperlinks
This should have tested the rel attribute value, but as it hasn't been doing that and it would be quite a bit of work, let's remove this instead.
--
wpt-commits: 25c665a93231027be5941838cecb3208e360d4b1
wpt-pr: 15357
Automatic update from web-platform-tests
Add screen orientation test: fire event before promise is resolved (#15267)
--
wpt-commits: 8ed64687560332642c7b34ebd16011ae5b01d99a
wpt-pr: 15267
Automatic update from web-platform-tests
XMLSerializer: Fix prefixed attribute serialization
... in a case where its owner element has xmlns:prefix of which prefix
is same as the attribute and namespace is not same as the attribute.
e.g.
el.setAttributeNS("uri1", "p:n", "v");
el.setAttributeNS(XMLNS_URI, "xmlns:p", "uri2");
ShouldAddNamespaceAttribute() checked only existence of xmlns:prefix in
the element, but we should check existence of (prefix, namespace URI)
pair in the scope according to the specification.
So, this CL adds 'recording the namespace information' step [1] defined
by the specification, and ShouldAddNamespaceAttribute() checks all
available prefixes in the scope.
[1] https://w3c.github.io/DOM-Parsing/#recording-the-namespace
Bug: 929035
Change-Id: I575e8f652ae45f7583202443cc72d5afe5faf59d
Reviewed-on: https://chromium-review.googlesource.com/c/1460643
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631058}
--
wpt-commits: 265330b7d26194cb60157a18ac399127d21f6b99
wpt-pr: 15340
Automatic update from web-platform-tests
decimal points in numbers
Tests that decimal points are allowed *before* digits (like `.1`) and *between* digits (like `0.1`), but not *after* digits (like `1.`).
Tests <https://github.com/w3c/csswg-drafts/issues/3599>
--
fix whitespace for lint
--
Name all tests uniquely
--
Merge pull request #15337 from web-platform-tests/tabatkins-patch-2
decimal points in numbers
--
wpt-commits: 5fdd036dbd18fa6d2e7cf235bd9acc625a6df22e, f17e215eaa37316f1489a7b62ab103d2a58a0d89, 31e1a1bb5fadb08749e4b8070ad0f19ec5ea1088, e2eb25aaa6dd3c512b172588f3400f9c25a410c3
wpt-pr: 15337
Automatic update from web-platform-tests
url whitespace consumption
Ensure that whitespace before or after the string in a url() results in a correct parse.
Tests https://github.com/w3c/csswg-drafts/issues/3600
--
Merge pull request #15339 from web-platform-tests/tabatkins-patch-3
url whitespace consumption
--
wpt-commits: e0b3c4cf2f69e816c6b83432968dc7fc83d700f6, 0de6fa5638c7e314a0391fae7f6bf496309fb65d
wpt-pr: 15339
Automatic update from web-platform-tests
[css-box] Inheritance, initial values (#15312)
Test that CSS Box Model properties do not inherit.
https://drafts.csswg.org/css-box-3/#property-index
--
wpt-commits: 35bd69423b10a361a969139ba0271896dced9691
wpt-pr: 15312
Automatic update from web-platform-tests
Set click count correctly to dispatch "dblclick" event
In order to dispatch the "dblclick" event to DOM by sending synthetic
mouse events, we have to check the most recent two mouse press events.
If their dispatched times and locations are close enough, we will set
the mouse event's click count to 2, which will generate the "dblclick"
event.
Bug: 606367
Change-Id: I049d6463c6bf1393c9e8b496662359eeeef7682b
Reviewed-on: https://chromium-review.googlesource.com/c/1413362
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630933}
--
wpt-commits: 1ddffbeeb6faed345ce7f999544ed1d29c7a203f
wpt-pr: 14911
Automatic update from web-platform-tests
Verify that contentDocument is updated during nested browsing context document parsing.
--
wpt-commits: ae6d56308684b97f30a01b455ce3eb205cba79aa
wpt-pr: 15268
Automatic update from web-platform-tests
Fix canonical form of rotate property.
Expected behavior is outlined in the spec here:
https://drafts.csswg.org/css-transforms-2/#individual-transform-serialization.
Summary:
* 2d serializes to just an angle.
* Axis must be specified for 3-D rotations. If the axis is parallel to the x, y or z axis, the appropriate axis name must be used.
Bug: 905274
Change-Id: I5d16f3301baf9720099e4b5b42a1b87077b97998
Reviewed-on: https://chromium-review.googlesource.com/c/1447844
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#630796}
--
wpt-commits: a01ac89be3f48fa64bd96d36ac1a65ac9074eb4f
wpt-pr: 15205
Automatic update from web-platform-tests
Make stability checks provide an explicit message for duplicate test names
--
wpt-commits: 23008e948bff4c245148cfcda2ebaa72149a2bb1
wpt-pr: 15330
Automatic update from web-platform-tests
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
Update mozprocess from 0.26 to 1.0.0
--
wpt-commits: 9a874520787308eecb14d85399cb5184efaf99ec, 999c546d4958eb649a71f0339563218a22f6d281, e032140d4ba4954c0704356f4848cc8f1d2dd590, ad09e7414f098c7833a65d336f01e76ba8c1dc15, a54f2b6ed9445d74fded895c45b561b1e7fd9314, 47bb668028ce2b7f6e564b47aee7ed12ce720532, f55469ea2fe1ed49f6b3f2d9701b793fc051bb67, 78c2264a4d9b28e89070670d6a73df470ae45aaf, 725876f98dc3fe1dd86c131b73724ac0e0a41147
wpt-pr: 15294
Automatic update from web-platform-tests
[css-grid] Overflow should be computed with the actual logical bottom
In order to compute the 'auto' height of the grid container, we set
temporarily a value based on the tracks' size. We can see this value as
a kind of 'intrinsic height'. Then, we call to the UpdateLogicalHeight
function to finally compute the grid container's actual logical height.
In order to compute the overflow area in the grid container we should
use the result of the ClientLogicalBottom function. However, we were
retrieving this value just after setting the tracks-based temporary
height, and before computing the actual logical height.
The consequence of this wrong logic is that empty grid areas may
affect the result of the ClientLogicalBottom and, as it's described
in the bug, conclude that there is a content overflow in the grid
container, even if such container has no grid items at all.
Since the grid itself is not a box, it can't contribute to the grid
container's content size; instead, its grid items should.
This change ensures that we always use the actual grid container's
logical bottom to properly compute the overflow area.
Bug: 928885
Change-Id: I05f86fbce06a83c0dbc0d5389bf0416763f8588a
Reviewed-on: https://chromium-review.googlesource.com/c/1459620
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#630735}
--
wpt-commits: aa6f52fc7b99559377c760a550e842438efa91a1
wpt-pr: 15284
