layout/reftests/bugs/370422-1.html changes the size of a fission iframe.
Bug 1615504 made sure the visible rect got to the child process. But there is still a failure mode where (I assume) all invalidations/painting of changing the document size in the iframe content process happens before the effects visible rect ipc msg arrives at the content process.
In this case we still need to invalidate even though we use the correct visible rect on the builder we need a dirty rect that includes the unveiled area.
Depends on D65888
Differential Revision: https://phabricator.services.mozilla.com/D65889
--HG--
extra : moz-landing-system : lando
Bug 1603714 showed there were `UntrustedModulesData` instances in which a load
event pointed to a module which did not exist in the modules list.
This patch adds `MOZ_DIAGNOSTIC_ASSERT` to the following places to narrow down
when it happened.
Given that the number of the impected users seems big (~200 crashes/day on Nightly),
we activate the assers with a probability of 1/16 (~12.5 crashes/day).
1. When processing load events
1-1. [Content] `UntrustedModulesProcessor::CompleteProcessing:`
Verify events of a trusted module were eliminated by `GetModulesTrust`
1-2. [Content] `UntrustedModulesData::AddNewLoads`:
Verify a new `ModuleRecord` matches the event
1-3. [Content] `UntrustedModulesProcessor::CompleteProcessing`:
Verify processed data after new items were appended.
2. When processed data is sent
2-1. [Content] `UntrustedModulesProcessor::GetAllProcessedData`:
Verify processed data before serialization.
2-2. [Content] `ParamTraits<mozilla::UntrustedModulesData>::WriteEvent`:
Verify processed data before transferring to the browser process
2-3. [Browser] `ParamTraits<mozilla::UntrustedModulesData>::ReadEvent`:
A final point to catch this integrity problem. We had an IPC error here.
Differential Revision: https://phabricator.services.mozilla.com/D59964
--HG--
extra : moz-landing-system : lando
The blocklist variable `BROWSER_PROCESS` did not work as expected. Entries
defined there were blocked not only in the browser process but also in the
child process.
This patch makes sure entries in `BROWSER_PROCESS` are blocked only in the
browser process.
Differential Revision: https://phabricator.services.mozilla.com/D65248
--HG--
extra : moz-landing-system : lando
If an addon is updated and moves permissions between required to optional, we
want to retain the previously granted permission so the extension does not have to
request the permission from the user again. We also handle permission removal
and changes to preferences based on permissions.
Differential Revision: https://phabricator.services.mozilla.com/D64696
--HG--
extra : moz-landing-system : lando
This patch contains two changes.
1. `AltSvcMapping::ProcessHeader` is not thread-safe, so dispatching an async task to do this.
2. `TRRService::Init` is called earlier before the user profile is loaded. If `network.trr.fetch_off_main_thread` is default to false and changed to true by users, TRR background thread would not be created.
Differential Revision: https://phabricator.services.mozilla.com/D65890
--HG--
extra : moz-landing-system : lando
Hopefully this comment would prevent a future contributor from
removing the copy operation.
Differential Revision: https://phabricator.services.mozilla.com/D55424
--HG--
extra : moz-landing-system : lando
This duplicates the peculiarities of the win64-cross/opt task, while adding
a rust-size dependency it was lacking.
Differential Revision: https://phabricator.services.mozilla.com/D65483
--HG--
extra : moz-landing-system : lando
If a system uses a custom shell instead of Windows Explorer,
`ShellExecuteByExplorer` always fails because it relies on explorer.exe,
but `ShellExecute` stil works because it's in-proc implementation.
We added a fallback for a local file to address Bug 1602726. This patch adds
a fallback for a uri.
Differential Revision: https://phabricator.services.mozilla.com/D63095
--HG--
extra : moz-landing-system : lando
Bug 1603714 showed there were `UntrustedModulesData` instances in which a load
event pointed to a module which did not exist in the modules list.
This patch adds `MOZ_DIAGNOSTIC_ASSERT` to the following places to narrow down
when it happened.
Given that the number of the impected users seems big (~200 crashes/day on Nightly),
we activate the assers with a probability of 1/16 (~12.5 crashes/day).
1. When processing load events
1-1. [Content] `UntrustedModulesProcessor::CompleteProcessing:`
Verify events of a trusted module were eliminated by `GetModulesTrust`
1-2. [Content] `UntrustedModulesData::AddNewLoads`:
Verify a new `ModuleRecord` matches the event
1-3. [Content] `UntrustedModulesProcessor::CompleteProcessing`:
Verify processed data after new items were appended.
2. When processed data is sent
2-1. [Content] `UntrustedModulesProcessor::GetAllProcessedData`:
Verify processed data before serialization.
2-2. [Content] `ParamTraits<mozilla::UntrustedModulesData>::WriteEvent`:
Verify processed data before transferring to the browser process
2-3. [Browser] `ParamTraits<mozilla::UntrustedModulesData>::ReadEvent`:
A final point to catch this integrity problem. We had an IPC error here.
Differential Revision: https://phabricator.services.mozilla.com/D59964
--HG--
extra : moz-landing-system : lando
We were using the old cargo-vendor, which tries to fetch dependencies in a way
that crates.io dislikes, leading to spurious timeouts.
Use the built-in command instead. We no longer need the --relative-path flag
because the built-in one uses a relative path by default.
MANUAL PUSH: Fixing tree closure, so need to push on CLOSED TREE.
Differential Revision: https://phabricator.services.mozilla.com/D65882
syncWithCacheIOThread() ensures that all pending events on IO thread are processed before we continue on the main thread, where we synchronously check the flag in the index
Differential Revision: https://phabricator.services.mozilla.com/D65757
--HG--
extra : moz-landing-system : lando
Note: while we can use time.monotonic in fetch-content, we can't in
mach artifact toolchain yet because it's still python2.
Differential Revision: https://phabricator.services.mozilla.com/D65690
--HG--
extra : moz-landing-system : lando
This is very basic, and just uses the button colors. Did this because I thought
that it was going to help me fix one test but it didn't in the end, feel free to
reject, or to tell me to land the cleanup somewhere else :)
Depends on D65674
Differential Revision: https://phabricator.services.mozilla.com/D65675
--HG--
extra : moz-landing-system : lando
Otherwise the rendering of stuff like:
<input type=range style="height: 300px">
Makes no sense. So this is closer to other widgets, and also happens to fix the
only test which is a real regression from non-native widget :)
Depends on D65673
Differential Revision: https://phabricator.services.mozilla.com/D65674
--HG--
extra : moz-landing-system : lando
This _almost_ fixes layout/reftests/forms/input/range/auto-size.html. It still
fails because of the variable-width track size :/
Differential Revision: https://phabricator.services.mozilla.com/D65673
--HG--
extra : moz-landing-system : lando
Christian Holler
Makoto Kato
Jeff Gilbert
Tim Nguyen
Timothy Nikkel
Toshihito Kikuchi
Mark Banner
eghitta
Shane Caraveo
Ian Neal
Ted Campbell
Steve Fink
Kershaw Chang
Yaron Tausky
Oana Pop Rus
Jan de Mooij
Thal
Mike Hommey
Sylvestre Ledru
Gabriele Svelto
championshuttler
Hector Zhao
Emilio Cobos Álvarez
Dale Harvey
Michal Novotny
Simon Giesecke