Bug 1447977 introduced a new implementation of evaluate.isCyclic
that was not based on JSON.stringify to overcome cyclic references
stored on Element prototypes.
This patch reverts the new behaviour and hides it behind an environment
variable MOZ_MARIONETTE_NEW_CYCLIC. This is useful so we can more
easily test the difference in automation.
MozReview-Commit-ID: 2xtNL596Imc
My best guess as to the failures here is that we're not actually
reaching the busyWait call by the time the interrupt callback fires,
and thus we're killing unrelated scripts.
MozReview-Commit-ID: GvCJzBcJlXm
Differential Revision: https://phabricator.services.mozilla.com/D2162
--HG--
extra : moz-landing-system : lando
Fix an issue in GeckoEditable where spans can be mistakenly deleted when
deleting text. The new code re-copies all spans to make sure similar
issues don't happen in the future.
MozReview-Commit-ID: G1fWsJkeTka
--HG--
extra : rebase_source : 4ed3d17c3793a8a61182e660fb47694ba3c67f00
Currently, we expect editing operations in
GeckoEditableSupport::OnImeReplaceText to cause synchronous text change
notifications. However, under e10s, text change notifications can be
asynchornous. The new code keeps track of active OnImeReplaceText calls,
and look for async text changes before replying to the calls.
MozReview-Commit-ID: INM3JLmQebK
--HG--
extra : rebase_source : ff5b728ef437fcd78e4e7eced9c9a537d4698dce
Fetches no longer need to be artifacts exposed via a 'fetch' task, they can
also be artifacts from a task's dependencies. The new format is:
fetches:
fetch:
- fetch-artifact-1.zip
- fetch-artifact-2.zip
build:
- build-artifact-1.zip
...
Specifying 'build' artifacts to fetch will error out if the task doesn't have
any build dependencies.
The 'fetch' key works the same as before, but it is now a special case. Unlike
'build' (or other dependencies), adding a fetch task's artifact here will
implicitly make our task depend on the corresponding fetch task. It will not
be an error.
Depends on D2028.
Differential Revision: https://phabricator.services.mozilla.com/D2102
--HG--
extra : moz-landing-system : lando
Specialized the code added in Bug 1412517 so that it will apply only for
date/time inputs. The rest will have the previous behaviour.
MozReview-Commit-ID: JCAruK4x3r1
--HG--
extra : rebase_source : e2c0fa13f4c3edcf0c1e2b1a3654144f4057a650
The test aims to check playback events and CSS events
MozReview-Commit-ID: Bo5OhC6AdGC
--HG--
extra : rebase_source : 7635890b84099bce14a7e2beac1fec56439d42c6
Added support for whitespace in source-level attributes
Extended C++ unti test CheckSsrc
Extended Rust unti test for ssrc
MozReview-Commit-ID: 1xiYyZBYf5o
--HG--
extra : rebase_source : 26d8ee11592e40fa1c25021b86953c72b14636a7
Effectively we compute the diff by lopping off the rounded part
of each rect where appropriate. This gets a bit weird to think
about with very mismatched radii, but I think it works out(?)
MozReview-Commit-ID: 472gx7Hw1Br
--HG--
extra : rebase_source : 817a84d78c98ac99797ab73b89f8c667189767d1
Before, the value had to conform to the iterator protocol. But this didn't
actually work; the generator was left in "running" state, so while you could
sort of simulate a `yield` by returning an object with `{done: true}`, the
generator would throw the next time it was used.
Now, `{return: value}` behaves as if the generator executed a `return`. The
generator is left in the "closed" state.
Before the initial yield, a forced return causes the generator to return a
value that may be silly. An enclosed test checks that it doesn't crash, but
please don't do that.
--HG--
extra : rebase_source : 2d056e40aed0982f0a42351c3c456422b96989da
extra : source : e03417b86b1e74a269ad94fcaeacf26bac4016e7
We will in fact delete this method later in the stack, but to understand those
coming patches, it helps to understand what's going on here.
--HG--
extra : rebase_source : a8532831cb37aab4e346a58db09a9c7a7496de1b