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;
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
Enable globally by default by blacklist directories outside of the ones we're enabling. Remove now unnecessary existing configurations.
Differential Revision: https://phabricator.services.mozilla.com/D4440
--HG--
extra : moz-landing-system : lando
Automatic changes by ESLint, except for manual corrections for .xml files.
Differential Revision: https://phabricator.services.mozilla.com/D4439
--HG--
extra : moz-landing-system : lando
The click status of a mouse action has to be carried forward
to the next "Perform Actions" call if the action sequence
hasn't been reset before.
--HG--
extra : rebase_source : 59c3ac95fc6a0e2f091dc0a83172b75bca57c367
Given that all internal states for the virtual devices are getting
cleared when releasing actions, also the timer for double click
event detection has to be canceled.
--HG--
extra : rebase_source : c555ce65f2abb96ad7e91323e309f2114a743a77
Also take the opportunity to add that change to mozilla_customizations.diff and
to correct the line endings in the files that it contains changes to.
--HG--
extra : rebase_source : 10df36760e1f8cc0e8b2f93b47e76c27dcc912cc
extra : source : 9a448a33f4b43ef8572d80bc7b27c7a831f122c2
