Add tests that check serialization and deserialization for indefinite script timeout
Differential Revision: https://phabricator.services.mozilla.com/D17148
--HG--
extra : moz-landing-system : lando
It fixes the regression from the transition to Serde (bug 1396821),
which accidentally denied unknown fields.
Differential Revision: https://phabricator.services.mozilla.com/D17634
--HG--
extra : moz-landing-system : lando
It fixes the regression from the transition to Serde (bug 1396821),
which accidentally denied unknown fields.
Differential Revision: https://phabricator.services.mozilla.com/D17634
--HG--
extra : moz-landing-system : lando
The window should always be restored first to the normal window state,
before a special state like fullscreen or minimized can be entered.
Right now this isn't done when going from a maximized window into
fullscreen mode, or when minimizing the window.
Differential Revision: https://phabricator.services.mozilla.com/D17472
--HG--
extra : moz-landing-system : lando
The crash happens when we try to reparent the absolute/fixed
positioned children to the non-column-span wrapper's absolute list.
When constructing the multicol container, we want it to be the
absolute/fixed position container, not the moz-column-content anonymous
blocks. Hence the modification in AppendFramesToParent() and
ConstructBlock().
Delete AdjustAbsoluteContainingBlock() because we'd like to reparent
absolute/fixed children to non-first continuation of block descendant of
multicol. And it doesn't crash anymore today.
Differential Revision: https://phabricator.services.mozilla.com/D16728
--HG--
extra : moz-landing-system : lando
When investigating the timeouts for wikia.com on Google Chrome I discovered differences in the way proxy configuration is interpreted. It meant that insecure sites such as wikia were not using the proxy when launched via mach, and now that wikia.com redirects to a secure site we get redirected to a site that is not in the recordings. I have resolved this by fixing the command line argument for the proxy to include all protocols. It was also necesary to allow communication with the control server by adding localhost to the pass-through hosts.
I also removed the trailing disable-sync command line argument that was introduced recently in error.
Differential Revision: https://phabricator.services.mozilla.com/D17869
--HG--
extra : moz-landing-system : lando
Ideally, formAttributeName would be a field on the prototype of each front,
but unfortunately, Firefox doesn't support ES Class's fields yet. So it is
put as an instance attribute instead.
This patch streamline the manually set actorID and the retrieval of actor ID
from root or target front's form into `getFront` helper method.
So that all the specific related to the lazy actor is now inside of this helper.
It also moves the special "this.manage(this)" to this helper.
We might be able to followup on this one and finally have only the root front
being self managed. But the initialize method makes it hard.
Note the special tweak made to devtools/client/responsive.html/manager.js
Hopefully this can be removed once the target classes are merged.
Depends on D15832
Differential Revision: https://phabricator.services.mozilla.com/D17615
--HG--
extra : moz-landing-system : lando
This changes the policy to use the pref and permissions rather than a boolean flag. Using permissions gets us proper settings on startup without introducing any new overhead. Going this way flips our tests around so rather than testing an override to turn off private browsing support, we test overrides to enable private browsing support.
Differential Revision: https://phabricator.services.mozilla.com/D14482
--HG--
extra : moz-landing-system : lando
Mars are now generated by separate repackage tasks, so we don't need mar tools
in L10n builds.
Differential Revision: https://phabricator.services.mozilla.com/D17161
--HG--
extra : moz-landing-system : lando
Some other bugs fixed the leaks in these directories, so the white
lists can be removed.
Differential Revision: https://phabricator.services.mozilla.com/D17290
--HG--
extra : moz-landing-system : lando
***
Bug 1514594: Part 3a - Change ChromeUtils.import to return an exports object; not pollute global. r=mccr8
This changes the behavior of ChromeUtils.import() to return an exports object,
rather than a module global, in all cases except when `null` is passed as a
second argument, and changes the default behavior not to pollute the global
scope with the module's exports. Thus, the following code written for the old
model:
ChromeUtils.import("resource://gre/modules/Services.jsm");
is approximately the same as the following, in the new model:
var {Services} = ChromeUtils.import("resource://gre/modules/Services.jsm");
Since the two behaviors are mutually incompatible, this patch will land with a
scripted rewrite to update all existing callers to use the new model rather
than the old.
***
Bug 1514594: Part 3b - Mass rewrite all JS code to use the new ChromeUtils.import API. rs=Gijs
This was done using the followng script:
https://bitbucket.org/kmaglione/m-c-rewrites/src/tip/processors/cu-import-exports.jsm
***
Bug 1514594: Part 3c - Update ESLint plugin for ChromeUtils.import API changes. r=Standard8
Differential Revision: https://phabricator.services.mozilla.com/D16747
***
Bug 1514594: Part 3d - Remove/fix hundreds of duplicate imports from sync tests. r=Gijs
Differential Revision: https://phabricator.services.mozilla.com/D16748
***
Bug 1514594: Part 3e - Remove no-op ChromeUtils.import() calls. r=Gijs
Differential Revision: https://phabricator.services.mozilla.com/D16749
***
Bug 1514594: Part 3f.1 - Cleanup various test corner cases after mass rewrite. r=Gijs
***
Bug 1514594: Part 3f.2 - Cleanup various non-test corner cases after mass rewrite. r=Gijs
Differential Revision: https://phabricator.services.mozilla.com/D16750
--HG--
extra : rebase_source : 359574ee3064c90f33bf36c2ebe3159a24cc8895
extra : histedit_source : b93c8f42808b1599f9122d7842d2c0b3e656a594%2C64a3a4e3359dc889e2ab2b49461bab9e27fc10a7
AVDs are identical to previous version, except that the config.ini files are updated
with a larger size for the /data partition.
--HG--
extra : rebase_source : 4eb406a33e47593bb7e7ff9dc34142516012d7ea
For shutdown crashes in wpt wse need to ignore the crashes for now
until we have a way of allowing specific ones. So just have a global
flag that permits this.
Differential Revision: https://phabricator.services.mozilla.com/D16836
Sometimes it's unclear which of the errors are leading to a
failure. For example wpt sometimes has PROCESS-CRASH lines that don't
contribute to a failure. To make this easier to understand record the
reason for the failure in the log so it appears in the summaries.
Differential Revision: https://phabricator.services.mozilla.com/D16835
Instead of printing one log message per line about the fact the output
was unstructured, just print one per group of unstructured lines.
Differential Revision: https://phabricator.services.mozilla.com/D16834
It can happen that a tab has an expected crash in wpt. As a result we
won't get a valid leak file for that content process. But this
shouldn't cause the tests to fail. In the absence of a more precise
mechanism we just disable that check for the tab process, but it would
be an improvement to know which processes crashed and ensure that only
those ended up with unexpected leak files.
Differential Revision: https://phabricator.services.mozilla.com/D16833
This behaviour was leading to intermittent failures with shutdown
crashes, as according to timing we would sometimes get a crash dump
file and sometimes not (or we would sometimes get a shutdown crash and
sometimes not). Until we either have the ability to allow certain
crashes or the ability to set multiple expected statuses, don't change
the test status when we find a process crashed (the crash will
still be logged).
Differential Revision: https://phabricator.services.mozilla.com/D16832
If we get a NoSuchWindow error from marionette, then something happend
that caused the window to disappear, which we can interpret as a
crash. This may not be true if we accidentially navigated the window
to file:// or something else that causes a remoteness change, but
those are basically marionette bugs so in the long term this should be
correct.
Differential Revision: https://phabricator.services.mozilla.com/D16830
Automatic update from web-platform-tests
[css-text] Remove "exploratory" comment for test backed up by the spec
The comment about this test being exploratory is wrong.
Assuming that the claim that
“people using indic scripts expect the user agent
to keep the orthographic syllable as a single unit”
is true, the spec definition's of typographic character/letter unit
are sufficient to justify the test.
--
wpt-commits: 691e737caf050c5aac0f9675409d73238a3f55d2
wpt-pr: 14575
Automatic update from web-platform-tests
TextDecoder: previous failure should not stick around
When the {fatal:true} option is used, the decode() calls throw rather
than generating U+FFFD on bad data. Subsequent decode() calls should
work as the codec state should be flushed (unless {stream:true} was
specified).
Blink was not flushing the codec state, so subsequent calls would
throw. Fix by flushing the codec state (instantiating a new codec),
and align the implementation's code flow/state more closely with the
spec. Also added a new WPT test case, based on the bug report.
Bug: 910292
Change-Id: Ia47b902b69a4b469341e272ed42bb6b05248c1d8
Reviewed-on: https://chromium-review.googlesource.com/c/1376656
Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617215}
--
wpt-commits: a093a659ed118112138f8a1ffba97a66c1ea8235
wpt-pr: 14509
