Otherwise the ShadowRoot for <use> or other internal ones may not get cloned
properly.
Differential Revision: https://phabricator.services.mozilla.com/D4756
--HG--
extra : moz-landing-system : lando
Use the unused 'p' bit in the version code to denote 64-bit builds, so
we have different version codes for 64-bit builds on aarch64 and x86-64.
Differential Revision: https://phabricator.services.mozilla.com/D4260
--HG--
extra : moz-landing-system : lando
make counter increased when trackers are found
Differential Revision: https://phabricator.services.mozilla.com/D4068
--HG--
extra : rebase_source : 90da79fbb83271b2f7a8460ebd02aa2abb635305
extra : source : c476aa79a8ca991dc8ea1e5c2eab98e442dad406
Introduce these new blocking state values:
const unsigned long STATE_COOKIES_BLOCKED_BY_PERMISSION = 0x10000000;
const unsigned long STATE_COOKIES_BLOCKED_TRACKER = 0x20000000;
const unsigned long STATE_COOKIES_BLOCKED_ALL = 0x40000000;
const unsigned long STATE_COOKIES_BLOCKED_FOREIGN = 0x80000000;
separate tracker counter API
Differential Revision: https://phabricator.services.mozilla.com/D4490
--HG--
extra : rebase_source : 2a786ca9d008e01e465d1d34951d07493c5c9d2b
extra : source : 9370432b26adcd6399e586190a47d4c8a8cdc56d
If we don't have a saved session, we do nothing. If somebody called setSession
beforehand, we continue using that session, otherwise we create a fallback
session in onAttachedToWindow().
If we have a saved session and nobody called setSession, we use the saved
session. If the saved session was closed and doesn't have a runtime, we use the
default runtime as a fallback.
If we have both a saved session and somebody already called setSession, we
transfer what can be transferred from the saved session, unless the saved
session is closed and the session from setSession is open.
If the saved session was open, we use its runtime as well going forward (since
transferring the state from an open session transfers the window and the runtime
as well), otherwise we keep the old mRuntime.
Differential Revision: https://phabricator.services.mozilla.com/D4711
--HG--
extra : moz-landing-system : lando
Last time it was updated is bug 1436208, and the crashes we patched it
for back then has been fixed upstream a few months later.
For some reason, they renamed the executable from llvm-dsymutil to
dsymutil.
Differential Revision: https://phabricator.services.mozilla.com/D4741
--HG--
extra : moz-landing-system : lando
Added an extra check for package name for a better user experience, because the push notifications with "about" protocol
in the URL message were still firing the chooser dialog.
Differential Revision: https://phabricator.services.mozilla.com/D4578
--HG--
extra : moz-landing-system : lando
Instead of stopping the foreground service whenever ACTION_PAUSE was triggered,
I created a new event where we notify the service to clear its foreground state.
Cleared usages of the NotificationManager and the onGoing attribute of the
MediaNotification because they are redundant. As of Android 4.3 a service in the
foreground state will always force the notification to be persistent and callling
stopForeground(false) will clear the onGoing flag while maintaining the notification.
Differential Revision: https://phabricator.services.mozilla.com/D4567
--HG--
extra : moz-landing-system : lando
so that such requests don't inadvertently reuse connections done that
might have used TRR.
MozReview-Commit-ID: 2bO4VCGSgOO
Differential Revision: https://phabricator.services.mozilla.com/D4693
--HG--
extra : moz-landing-system : lando
This allows screen reader users to determine the context of various controls when tabbing through them.
Specific changes:
1. Describe the "Cookies and Site Data" group using the disk space indicator; e.g. "Your stored cookies, site data and cache are currently using 315 MB of disk space."
2. Associate the description for the "Content Blocking" group; i.e. "Block third-party content, like ads or code..."
3. Correct association of the label for the "Do Not Track" setting; i.e. 'Send websites a “Do Not Track” signal that you don’t want to be tracked'
4. Associate the label for the "Permissions" group.
5. Make each permission a labelled group so the user knows what the various "Settings…" buttons are for.
6. Associate the label for the "Data Collection and Use" group.
Differential Revision: https://phabricator.services.mozilla.com/D4638
--HG--
extra : moz-landing-system : lando
replaceTabsWithWindow calls replaceTabWithWindow to create a new window window with a first tab.
But unlike the later function, the former cited function don't take an object param (aOptions) containing informations such as the mouse position (which helps set the new window position).
To adress the issue, we added support for passing an option param to replaceTabsWithWindow which just transferts the param to replaceTabWithWindow.
Differential Revision: https://phabricator.services.mozilla.com/D4735
--HG--
extra : moz-landing-system : lando
This is a regression of bug 1486370.
Unlink of Selection removes all nsISelectionListener first, then, it removes
all its ranges since it does not want to notify the changes anymore.
After bug 1486370, Selection starts to store only bool flag whether it should
notify AutoCopyListener of selection changes. So, unless it sets the bool flag
to false in Unlink, it'll notify selection change caused by Unlink.
Differential Revision: https://phabricator.services.mozilla.com/D4690
--HG--
extra : moz-landing-system : lando
This does a few things that should help:
(1) Run the timeout only after resize events have stopped.
(2) Increase the timeout from 30ms to 100ms. It doesn't need to be so fast.
(3) Add a parameter to formatValue that bypasses actually formatting the value and instead only ensures the host is visible. There's no need in this case to keep removing the formatting and then adding it back. Having a "formatValue" method take a parameter to skip formatting is kind of weird, though. At first I tried factoring out the make-host-visible part, but that requires also factoring out all the logic that determines whether the value is a formattable URL, and that ended up being ugly. I'm open to better ideas.
Based on an earlier patch by Marco Bonardo <mbonardo@mozilla.com>
Differential Revision: https://phabricator.services.mozilla.com/D4502
--HG--
extra : moz-landing-system : lando
From the PIP window the user can either return to the fullscreen app or exit
it entirely.
Fullscreen and subsequently hiding the status bar should only be done if the
user is returning to the app.
Differential Revision: https://phabricator.services.mozilla.com/D4676
--HG--
extra : moz-landing-system : lando
Emilio Cobos Álvarez
Chris Manchester
Ed Lee
Jared Wein
Sam Foster
Jim Chen
Mark Banner
Coroiu Cristina
Liang-Heng Chen
Martin Stransky
Andrea Marchesini
Andrew Halberstadt
Jan Henning
Dimi Lee
Mike Hommey
Andrei Lazar
Vlad Baicu
Daniel Stenberg
Paolo Amadini
Margareta Eliza Balazs
Julian Descottes
James Teh
Nicholas Nethercote
Gurzau Raul
Jesse Schwartzentruber
Abdoulaye O. Ly
Cameron McCormack
Masayuki Nakano
Drew Willcoxon
Petru Lingurar
Robert Helmer