Mechanical change from Matcher::match(...) to Matcher::operator()(...).
This will now permit the use of generic lambdas, and facilitate the
implementation of multi-lambda match.
Differential Revision: https://phabricator.services.mozilla.com/D24889
--HG--
extra : moz-landing-system : lando
Navigating with Alt + arrow keys on OSX when the autocomplete popup
was open wasn't closing the popup, which could lead to weird behavior.
The test asserting arrow keys behavior is modified to ensure
this works as expected on all the different platforms.
Differential Revision: https://phabricator.services.mozilla.com/D25378
--HG--
extra : moz-landing-system : lando
I also updated the logic to properly cycle through the visible search engines list
and added a unit test that was missing, somehow.
Differential Revision: https://phabricator.services.mozilla.com/D25368
--HG--
extra : moz-landing-system : lando
This allows suspending and resuming the context from the debugger without having
observable side-effects.
Differential Revision: https://phabricator.services.mozilla.com/D24915
--HG--
extra : moz-landing-system : lando
Since reporting intervals are ~1 day/1 session, the Origin Telemetry prototype
must support the possibility that multiple origins will be recorded for the
same metric.
For example, if the user is sampled to record two pageloads where the same
ultra-common tracker is present and blocked we must record that tracker as
having been blocked twice.
This requires a bit of a shift in storage and plaintext snapshot. Instead of
being an array of origins with duplicates, now we're storing origins as a bag
(aka multiset, aka hashtable of origin->count).
Differential Revision: https://phabricator.services.mozilla.com/D25283
--HG--
extra : moz-landing-system : lando
Content Blocking's list is longer than the largest bool vector size supported
by PrioEncoder, so we need to split the list into shards before encoding.
This means we need to use the metric name and shard number together to identify
the encoding so it's possible to decode it later.
While I'm here, restructure GetEncodedSnapshots to make my life easier when I
eventually try to put the heavy lifting on its own thread. There's a clearer
split now between JS stuff and non-JS stuff.
Differential Revision: https://phabricator.services.mozilla.com/D25129
--HG--
extra : moz-landing-system : lando
In order to notify the "prio" ping when we reach the data limit, we need to
keep an accounting of how many prioData elements we'd need to encode what's in
storage.
This also adds the pref reading and topic notification code for the
"origin-telemetry-storage-limit-reached" topic that the "prio" ping observes.
Differential Revision: https://phabricator.services.mozilla.com/D25127
--HG--
extra : moz-landing-system : lando
When `Target.setDiscoverTargets` is called, one `Target.targetCreated` event
should be sent per already opened tab.
Differential Revision: https://phabricator.services.mozilla.com/D25558
--HG--
extra : moz-landing-system : lando
Increase the minimum width of the custom method value to make all options appear comfortably.
Fix Custom Request Panel header title wrap bug.
Style & position Custom Requeset Panel buttons properly.
Differential Revision: https://phabricator.services.mozilla.com/D23252
--HG--
extra : moz-landing-system : lando
Converted StatusBar to a Component and added a `shouldComponentUpdate` method to prevent unnecessary updates.
Differential Revision: https://phabricator.services.mozilla.com/D24599
--HG--
extra : moz-landing-system : lando
The propType is changed to *not* required as the function is
only passed when the grouping pref is true.
Differential Revision: https://phabricator.services.mozilla.com/D25560
--HG--
extra : moz-landing-system : lando
TEST 18 of layout/style/test/test_font_loading_api.html is fragile on Android in the sense
that adding a new mochitest in an irrelevant directory (e.g. layout/svg/test)
might cause a failure rate close to 50%. See Comment 34 in Bug 1455824.
Increasing SimpleTest.requestLongerTimeout() doesn't make much difference, see
https://treeherder.mozilla.org/#/jobs?repo=try&revision=c954cc8621372252a500fe1db04fb06edd636d9c.
Comment 43 and 44 from Testing team suggested the drastical failure increasing
is probably only related to different task grouping when a new testcase is added
elsewhere.
We should probably disable it now on Android platform, because it might cause
false-negative and confusion when someone lands an unrelated mochitest in
an irrelevant directory.
Differential Revision: https://phabricator.services.mozilla.com/D25718
--HG--
extra : moz-landing-system : lando
Stop using --panel-disabled-color for subviewbutton shortcuts (where the subviewbutton is also a menuitem)
Differential Revision: https://phabricator.services.mozilla.com/D25521
--HG--
extra : moz-landing-system : lando
Fallback code is now generated (as a single JitCode instance) when we create the
JitRuntime.
In ICScript::Create we can now allocate the fallback stubs directly (we no
longer need a Compiler class for each fallback stub) because we no longer have
to handle the compile-code case.
Differential Revision: https://phabricator.services.mozilla.com/D24360
--HG--
extra : moz-landing-system : lando
