Remove eval() from updates.js
Refactor code to make mapping of pageids to js-objects obsolete
Remove now unnecessary object attributes from wizard pages in updates.xul
Differential Revision: https://phabricator.services.mozilla.com/D25921
--HG--
extra : moz-landing-system : lando
This patch adds the number of dropped frames for each step of the process
(read/sink/compositor) and gives us more insight about where frames are
dropped, as opposed to the getVideoPlaybackQuality() API which gives the grand
total.
Differential Revision: https://phabricator.services.mozilla.com/D27488
--HG--
extra : moz-landing-system : lando
Configure the lmdb-rkv-sys Rust crate to use a smaller MDB_IDL_LOGN size in order to reduce allocations when opening an LMDB environment in read-write mode.
@glandium I adopted the configuration strategy you suggested of creating a "feature" for each reasonable value for the MDB_IDL_LOGN macro. Fortunately, the range of reasonable values is fairly small.
@nanj Based on your evalution in https://github.com/mozilla/lmdb/pull/2, a value of "9" for this macro should aggressively reduce the allocations while still supporting our existing use cases. But I'm open to increasing it, if you think a higher initial value would be preferable.
Differential Revision: https://phabricator.services.mozilla.com/D27559
--HG--
extra : moz-landing-system : lando
And tell webrender to do them itself (they have fundamental mismatches in how they
define shadow bounds).
Differential Revision: https://phabricator.services.mozilla.com/D26845
--HG--
extra : moz-landing-system : lando
These are trivially different. I couldn't find a cause for the
difference, so I am just regenerating them.
Differential Revision: https://phabricator.services.mozilla.com/D27544
--HG--
extra : moz-landing-system : lando
... and ensure that, if we do cleanup, we generate frames for every document.
Differential Revision: https://phabricator.services.mozilla.com/D25133
--HG--
extra : moz-landing-system : lando
We discussed this a bit in Orlando. Essentially, we want to run cleanup
operations in texture_cache before all documents' frames, and then be
able to ensure that every document generates a frame, because otherwise
we will run into problems with evicted cache items used by non-updating-
but-still-rendering documents. Accordingly, we need an endpoint to
lump all of the transactions that generate frames together. This adds
that and builds out all of the plumbing necessary.
Differential Revision: https://phabricator.services.mozilla.com/D25132
--HG--
extra : moz-landing-system : lando
It's easier this way than fixing who knows how many Webextension APIs that have
learned from Desktop that there is no tab #0 and that therefore refuse to work
in our first tab.
We'll also make a similar change to GeckoView's stub implementation of the tab
API because that affects Custom Tabs and PWAs in Fennec for now.
The tests for tab ID 0 are therefore no longer required - they were added in a
previous attempt to fix the Webextension APIs themselves, which was ultimately
never carried through to completion, though.
Differential Revision: https://phabricator.services.mozilla.com/D26431
--HG--
extra : moz-landing-system : lando
Changes:
- added windows10-aarch64 to the filter for fuzzy, to require `--full` in order to trigger jobs
- return False for any test tasks that contain windows10-aarch64 to prevent users using old try syntax from overwhelming the limited number of hardware
Differential Revision: https://phabricator.services.mozilla.com/D27590
--HG--
extra : moz-landing-system : lando
Now the spec cleary says that we don't need to propagate body's
scroll-padding value to the document viewport since
https://github.com/w3c/csswg-drafts/issues/3740, so we don't need to care about
GetViewportScrollStylesOverrideElement() at all.
This change fixes the crash test case in this commit, but it's not sufficient.
In the next patch, we will fix another crash case.
Differential Revision: https://phabricator.services.mozilla.com/D27422
--HG--
extra : moz-landing-system : lando
The only reason this wasn't already working is that propertyOrMethodName()
relied on a Semi token to help it recognize a FieldDeclaration without an
Initializer. This obviously can't work if the semicolon isn't there, so this
patch makes Field the default case.
That means the caller, classMember(), must be prepared for
propertyOrMethodName() to succeed with PropertyType::Field when in fact maybe
there's nothing but gibberish coming up; but we already handle that.
Differential Revision: https://phabricator.services.mozilla.com/D26038
--HG--
extra : moz-landing-system : lando
Andrew Halberstadt
Jan Varga
Jim Blandy
Chris Manchester
Jonas Allmann
Byron Campen [:bwc]
GettyOrawo
Andreea Pavel
Zibi Braniecki
Nihanth Subramanya
Tarek Ziadé
Myk Melez
danielleleb
Mats Palmgren
Cameron McCormack
Ethan Glasser-Camp
Coroiu Cristina
Miko Mynttinen
Barret Rennie
Alexis Beingessner
Doug Thayer
Jan Henning
Edwin Gao
Jared Hirsch
Cosmin Sabou
Kirk Steuber
James Willcox
Kartikaya Gupta
Hiroyuki Ikezoe
Eugen Sawin
Eugen Sawin
Jason Orendorff