This is not an error in the same way as a download failure, and should not be reported as one.
An Info message is sufficient.
Also suppress "unknown" location in messages about @font-face rules, as it is not useful,
pending a proper fix (bug 1450903).
Differential Revision: https://phabricator.services.mozilla.com/D50346
--HG--
extra : moz-landing-system : lando
Lots of these callbacks have a non-`void*` final parameter, which UBSAN
complains about. This commit changes them to have a `void*` parameter.
This requires undoing the machinery added in the first two commits of bug
1473631: `TypePrefChangeFunc` and `PREF_CHANGE_METHOD`. The resulting code is
simpler (which is good) and more boilerplate-y (which is bad) but avoids the
undefined behaviour (which is good).
Differential Revision: https://phabricator.services.mozilla.com/D50901
--HG--
extra : moz-landing-system : lando
- When partial present is not valid, ensure that a single dirty
rect the entire size of the framebuffer is returned.
- Ensure that we never return an empty dirty rect. If nothing is
dirty, the returned dirty rects array is empty, which can be
used by the client to completely skip calling Present.
- Remove partial present Multi mode (for now). This mode has
some issues with overlapping tiles which can be resolved as
a follow up.
This should allow enabling partial present for a single dirty rect,
which covers most common cases. We can re-implement the more
complicated Multi partial present mode if / when we find pages
where supporting multiple partial present rects is a good win.
Differential Revision: https://phabricator.services.mozilla.com/D51332
--HG--
extra : moz-landing-system : lando
Also add assertions that enforce that fission requires
DocumentChannel.
Also Removed the use of `rv` from the return statement at the end of
OnStartRequest(nsIRequest.
Differential Revision: https://phabricator.services.mozilla.com/D49101
--HG--
extra : moz-landing-system : lando
the URL moz://a redirects to mozilla's website, Because it redirects to
https we want to use documentchannel.
Depends on D49100
Differential Revision: https://phabricator.services.mozilla.com/D51227
--HG--
extra : moz-landing-system : lando
We cache the path in AnimationInfo for layers, and in
CompsoitorAnimationStorage for web-renderer.
Differential Revision: https://phabricator.services.mozilla.com/D50013
--HG--
extra : moz-landing-system : lando
This also includes the implementation of SetAnimatable, FromAnimatable,
and merge the final matrix with motion path.
Besides, we always use PathBuilderSkia for calculating the gfx::Path for
web-renderer.
Differential Revision: https://phabricator.services.mozilla.com/D50011
--HG--
extra : moz-landing-system : lando
We need to pass these two types into the compositor, so we need a better
way to serialize these rust types. We use serde and bincode to
serialize/deserialize them, and use ByteBuf to pass the &[u8] data
through IPC. We define StyleVecU8 for FFI usage only.
Differential Revision: https://phabricator.services.mozilla.com/D50688
--HG--
extra : moz-landing-system : lando
On the compositor thread in GPU process (i.e. web-renderer), gfxPlatform() is
not initialized, so we don't have the DrawTarget information.
Fortunately, all we need is to calculate the motion point and direction
vector, so we don't have to care about which backend we use.
Therefore, make PathBuilder as a parameter, so we can just pass a valid
PathBuilder on the compositor thread. For main thread (i.e. content
process), using the original way is fine.
Differential Revision: https://phabricator.services.mozilla.com/D50010
--HG--
extra : moz-landing-system : lando
The current implementation uses nsIFrame to get everything. However, we
want to reuse ResolveMotionPath() on the compositor thread (in the parent
process), so we need to refactor this function to avoid using nsIframe
everywhere.
Differential Revision: https://phabricator.services.mozilla.com/D50009
--HG--
extra : moz-landing-system : lando
I'd like to add some new data type for motion path, so it'd be great to
put all of them in an independent file.
Differential Revision: https://phabricator.services.mozilla.com/D50008
--HG--
extra : moz-landing-system : lando
This test is setup to run both with and without the pref
"devtools.responsive.browserUI.enabled" set. Ideally, we can find a
way to refactor this structure into something that can be put into
devtools/client/responsive/test/browser/head.js, and other helper
functions in that file can be modified to work with the pref on or
off.
Differential Revision: https://phabricator.services.mozilla.com/D51022
--HG--
extra : moz-landing-system : lando
This obviously only improves the situation when a subsequent window is the
same size as the last window that was opened.
Differential Revision: https://phabricator.services.mozilla.com/D50527
--HG--
extra : moz-landing-system : lando
The changes in bug 1583575 cause an additonal event to call the `ContentDelegate`,
so the test proceeds without waiting specifically for `onFullScreen` to be called.
This patch annotates the `onFullScreen` overrides to ensure that we're waiting
on the correct event for these test cases.
Differential Revision: https://phabricator.services.mozilla.com/D51195
--HG--
extra : moz-landing-system : lando
This makes the behaviour for touch-drags match the behaviour we already have
for pan gesture events.
Depends on D51201
Differential Revision: https://phabricator.services.mozilla.com/D51202
--HG--
extra : moz-landing-system : lando
This patch makes several changes in order to enable it in Fission.
1. We modify the way how testing child window and iframe get the test
number. It used to get the test number through opener/parent. However,
the property of the opener/parent is inaccessible if it is cross site.
So, for load tests, we use url parameter to propagate the test number to
child window. For write tests, we directly write the test number in the
markup.
2. We change to use SpecialPowers.spawn() to access testing window since
they could be cross origin from the test script.
In addition, we add comments for better understanding the test script
itself.
Differential Revision: https://phabricator.services.mozilla.com/D51005
--HG--
extra : moz-landing-system : lando
This patch uses the low memory resource notification facility to detect
scenarios where physical memory is running low without polling. This is a
significant change compared to the previous behavior which measured both
available virtual memory (only on 32-bit builds) and available commit space.
Since we're not trying to avoid OOMs anymore we don't save memory reports
anymore when hitting a low-memory condition.
Differential Revision: https://phabricator.services.mozilla.com/D50471
--HG--
extra : moz-landing-system : lando
Manifest V3 functionality. This applies CSP on the webextension content scripts using either a default csp or an
extension provided csp. It will remain pref'd off but is available for developers to test against, as well as for future
validation of chrome compatibility.
Differential Revision: https://phabricator.services.mozilla.com/D48107
--HG--
extra : moz-landing-system : lando
This patch adds support for including content_scripts CSP in the extensions
manifest, along with all interfaces necessary to access the CSP value. This does not
implement actual use of the CSP for content scripts.
Differential Revision: https://phabricator.services.mozilla.com/D46824
--HG--
extra : moz-landing-system : lando
Daosheng Mu
Jonathan Kew
yulia
Dan Glastonbury
Oriol Brufau
Nicholas Nethercote
Jason Laster
Glenn Watson
Martin Stransky
Dragana Damjanovic
Cosmin Sabou
Tom Tung
Gurzau Raul
Csoregi Natalia
Edouard Oger
Paul Bone
Boris Chiou
Brad Werth
Aaron Klotz
Ehsan Akhgari
Botond Ballo
Tim Huang
Erica Wright
thomasmo
Nils Ohlmeier [:drno]
Anny Gakhokidze
Sorin Davidoi
Gabriele Svelto
Shane Caraveo