- Jan 16, 2019
-
-
Mike Hommey authored
So that individual parts can be reused downstream. Depends on D16620 Differential Revision: https://phabricator.services.mozilla.com/D16621 --HG-- extra : moz-landing-system : lando
-
Mike Hommey authored
Depends on D16619 Differential Revision: https://phabricator.services.mozilla.com/D16620 --HG-- extra : moz-landing-system : lando
-
Mike Hommey authored
Depends on D16618 Differential Revision: https://phabricator.services.mozilla.com/D16619 --HG-- extra : moz-landing-system : lando
-
- Jan 15, 2019
-
-
Mike Hommey authored
Bug 1520340 - Use js_options instead of exported variables from old-configure for a few variables. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D16618 --HG-- extra : moz-landing-system : lando
-
- Jan 16, 2019
-
-
Dragana Damjanovic authored
Differential Revision: https://phabricator.services.mozilla.com/D15022 --HG-- extra : moz-landing-system : lando
-
Dragana Damjanovic authored
Differential Revision: https://phabricator.services.mozilla.com/D15024 --HG-- extra : moz-landing-system : lando
-
Brad Werth authored
The tests for Bug 1133905 all compare the visibility of scrollbars with differently-sized css viewports. This patch has some affect on the viewport sizing that I don't understand, and it causes some of the tests to start passing and some to start failing. The test for Bug 12421722 has elements sized to height 100% and checking for the presence or absence of scrollbars. In this case the patch appears to increase the css viewport height and decrease the width -- again for reasons I don't understand -- and this affects the scrollbar sizes. Differential Revision: https://phabricator.services.mozilla.com/D16078 --HG-- extra : moz-landing-system : lando
-
Brad Werth authored
Testing the initial value of innerWidth and innerHeight is not really viable when the visual viewport has been set by the opener, but constrained by the device. The returned value differs between the desktop and mobile browsers because of the device constraints. The simplest thing to do is to test the CSS viewport and ensure that the innerWidth values can be set. Differential Revision: https://phabricator.services.mozilla.com/D15996 --HG-- extra : moz-landing-system : lando
-
Brad Werth authored
Bug 1504659 Part 3: Add tests of viewport RDM scroll behavior, with and without touch simulation. r=gl Differential Revision: https://phabricator.services.mozilla.com/D13174 --HG-- extra : moz-landing-system : lando
-
Brad Werth authored
Bug 1504659 Part 2: Update innerWidth/Height getters and setters to better handle overridden visual viewports. r=botond Differential Revision: https://phabricator.services.mozilla.com/D15995 --HG-- extra : moz-landing-system : lando
-
Brad Werth authored
Bug 1504659 Part 1: Make RefreshVisualViewportSize allow non-APZ zooming, and call it during RefreshViewportSize. r=botond Differential Revision: https://phabricator.services.mozilla.com/D13173 --HG-- extra : moz-landing-system : lando
-
Cosmin Sabou authored
--HG-- rename : testing/profiles/unittest-stability/extensions/README.txt => testing/profiles/unittest/extensions/README.txt rename : testing/profiles/unittest-stability/user.js => testing/profiles/unittest/user.js
-
Tim Nguyen authored
Differential Revision: https://phabricator.services.mozilla.com/D16753 --HG-- extra : moz-landing-system : lando
-
Thomas Nguyen authored
We should use parent document's referrer uri and referrer policy in this case Differential Revision: https://phabricator.services.mozilla.com/D16551 --HG-- extra : moz-landing-system : lando
-
Dzmitry Malyshau authored
The old vector recycler had a few problems: 1. shrinking to fit would be inevitably followed by re-allocation, since it's unlikely that the consequent sizes are below the immediately followed frames 2. shrinking before clearing means that the existing contents are copied over, which is a waste The new code has more complicated logic for recycling, aimed at reducing heap allocations. It's also collecting the statistics. Differential Revision: https://phabricator.services.mozilla.com/D16496 --HG-- extra : moz-landing-system : lando
-
Gabriele Svelto authored
Differential Revision: https://phabricator.services.mozilla.com/D15524 --HG-- extra : moz-landing-system : lando
-
Gabriele Svelto authored
Differential Revision: https://phabricator.services.mozilla.com/D16688 --HG-- extra : moz-landing-system : lando
-
Wes Kocher authored
The unittest/user.js file contained a mix of preferences that ensure tests can run (switching web services to dummy servers to prevent hitting networks, etc) and preferences that enable features that aren't shipping by default (turning on touch events, enabling experimental css features, etc). In the future, we're going to want to run tests of only the features that are being shipped in release builds (or in beta builds, or in esr builds, etc), so we need to move feature-enabling preferences into a different file to make it possible to run tests with various sets of features enabled. This commit just moves feature-enabling prefs into a new file and then includes that file everywhere unittest prefs were already being included, so it should have no functional difference in the set of preferences being set in test runs. Differential Revision: https://phabricator.services.mozilla.com/D16123 --HG-- rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-features/extensions/README.txt rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-stability/extensions/README.txt rename : testing/profiles/unittest/user.js => testing/profiles/unittest-stability/user.js extra : moz-landing-system : lando
-
Aaron Klotz authored
Bug 1520617: LauncherRegistryInfo - when the image timestamp changes, only avoid clearing start timestamps when force disabled; r=mhowell Differential Revision: https://phabricator.services.mozilla.com/D16752 --HG-- extra : moz-landing-system : lando
-
Thomas Daede authored
Differential Revision: https://phabricator.services.mozilla.com/D16615 --HG-- extra : moz-landing-system : lando
-
Glenn Watson authored
Differential Revision: https://phabricator.services.mozilla.com/D16740 --HG-- extra : moz-landing-system : lando
-
Michael Ratcliffe authored
Differential Revision: https://phabricator.services.mozilla.com/D16721 --HG-- extra : moz-landing-system : lando
-
Steve Fink authored
Differential Revision: https://phabricator.services.mozilla.com/D16738 --HG-- extra : moz-landing-system : lando
-
Aaron Klotz authored
Differential Revision: https://phabricator.services.mozilla.com/D16731 --HG-- extra : moz-landing-system : lando
-
Dzmitry Malyshau authored
When scroll frames are created, and no explicit parent is provided, the old code used to take the ClipID from the c/s stack. The stack has been removed on WR side, and this parent assignment got lost. This change takes the SpatialID from the top of the stack on Gecko side to replicate the old behavior. Differential Revision: https://phabricator.services.mozilla.com/D16732 --HG-- extra : moz-landing-system : lando
-
Jared Wein authored
Bug 1518786 - Remove translations from the pending queue if there is a caller that is waiting on the specific translations. r=zbraniecki Differential Revision: https://phabricator.services.mozilla.com/D16588 --HG-- extra : moz-landing-system : lando
-
Jared Wein authored
Bug 1518786 - Wait until Fluent strings have been applied before sizing the window to content. r=Gijs Differential Revision: https://phabricator.services.mozilla.com/D16587 --HG-- extra : moz-landing-system : lando
-
Dragana Damjanovic authored
Differential Revision: https://phabricator.services.mozilla.com/D16616 --HG-- extra : moz-landing-system : lando
-
Alastor Wu authored
Bug 1520088 - part5 - add pref to control whether blacklist can override the default setting. r=cpearce Differential Revision: https://phabricator.services.mozilla.com/D16640 --HG-- extra : moz-landing-system : lando
-
Alastor Wu authored
Differential Revision: https://phabricator.services.mozilla.com/D16581 --HG-- extra : moz-landing-system : lando
-
Alastor Wu authored
The autoplay checking for media element has 4 different phases, 1. check whether media element itself meets the autoplay condition 2. check whethr the site is in the autoplay whitelist 3. check global autoplay setting and check wether the site is in the autoplay blacklist. 4. check whether media is allowed under current blocking model (click-to-play or user-gesture-activation) Differential Revision: https://phabricator.services.mozilla.com/D16525 --HG-- extra : moz-landing-system : lando
-
Alastor Wu authored
Ensure we can always see the debug log for the autoplay result. Differential Revision: https://phabricator.services.mozilla.com/D16524 --HG-- extra : moz-landing-system : lando
-
Alastor Wu authored
Bug 1520088 - part1 : let 'IsMediaElementAllowedToPlay()' only check media element's attributes r=cpearce We would like to have different phases checking for autoplay, the first phase is to check media element itself, so we need to move other non-related checkings out from 'IsMediaElementAllowedToPlay()'. Differential Revision: https://phabricator.services.mozilla.com/D16523 --HG-- extra : moz-landing-system : lando
-
Ricky Rosario authored
MozReview-Commit-ID: IkH9is3LbUS Differential Revision: https://phabricator.services.mozilla.com/D16312 --HG-- extra : moz-landing-system : lando
-
Agboola Mukhtar authored
Differential Revision: https://phabricator.services.mozilla.com/D16609 --HG-- extra : moz-landing-system : lando
-
Emilio Cobos Álvarez authored
Bug 1509717 removed Gecko's definition of StyleBorderStyle to use the Rust one. The Rust version was ordered in a different way, and the table code relied on the order in order to build the mapping for border conflict resolution. Simplify this mapping now that border constants are ordered in terms of priority, see the comment on top of `enum BorderStyle`. Differential Revision: https://phabricator.services.mozilla.com/D16565 --HG-- extra : moz-landing-system : lando
-
Cosmin Sabou authored
Backed out 2 changesets (bug 1516022) for mochitest failures on browser_editcontrols_update. CLOSED TREE Backed out changeset 4fae3add610f (bug 1516022) Backed out changeset c683fbe0b984 (bug 1516022)
-
ui.manish authored
Differential Revision: https://phabricator.services.mozilla.com/D16631 --HG-- extra : moz-landing-system : lando
-
Yura Zenevich authored
Bug 1514856 - scale the text node snapshots down to normal size when text is too big or is zoomed in. r=pbro MozReview-Commit-ID: IzRo5nA94Fd Differential Revision: https://phabricator.services.mozilla.com/D15114 --HG-- extra : moz-landing-system : lando
-
Yura Zenevich authored
Bug 1514856 - move image data array traversal to worker thread when calculating contrast ratio for text nodes. r=jdescottes,ochameau MozReview-Commit-ID: K3twiMih7e9 Differential Revision: https://phabricator.services.mozilla.com/D15113 --HG-- rename : devtools/server/actors/utils/accessibility.js => devtools/server/actors/accessibility/contrast.js extra : moz-landing-system : lando
-