This override has no effect in CoreAnimation-backed windows. The upcoming
patches will implement an alternative approach.
Differential Revision: https://phabricator.services.mozilla.com/D22644
--HG--
extra : moz-landing-system : lando
The synchronous paint was only needed a long time ago when we were calling this
method during drawRect. We're not doing that any more, we usually call it from
viewWillDraw now. But even at the time, forcing a synchronous paint *within*
a paint was extremely sketchy, so best just to remove the code.
Differential Revision: https://phabricator.services.mozilla.com/D22642
--HG--
extra : moz-landing-system : lando
When `nsContentUtils::DispatchInputEvent()` dispatches `input` event, the
editor's value was changed by somebody. In this case, it needs to update
the valid state **and** notify to update the style.
(Note that I'm not sure whether this is right approach.)
Differential Revision: https://phabricator.services.mozilla.com/D25029
--HG--
extra : moz-landing-system : lando
In particular, it looks like this alignment is required by the Intel driver on
macOS if you want to avoid CPU copies.
It was already known that the efficiency gains from ClientStorage only
materialize if you follow certain restrictions:
- The textures need to use the TEXTURE_RECTANGLE_ARB texture target.
- The textures' format, internalFormat and type need to be chosen from a small
list of supported configurations. Unsupported configurations will trigger
format conversions on the CPU.
- The GL_TEXTURE_STORAGE_HINT_APPLE may need to be set to shared or cached.
- glTextureRangeAPPLE may or may not make a difference.
It now appears that the stride alignment is another requirement:
When uploading textures which otherwise comply with the above requirements, the
Intel driver will still make copies using the CPU if the texture's stride is not
32-byte aligned. These CPU copies are reflected in a high CPU usage (as observed
in Activity Monitor) and they show up in profiles as time spent inside
_platform_memmove under glrUpdateTexture.
However, when uploading 32-byte stride aligned textures which comply with the
above requirements, this CPU usage goes away. There might still be hardware
copies behind the scenes, but they no longer take up CPU time.
Differential Revision: https://phabricator.services.mozilla.com/D25316
--HG--
extra : moz-landing-system : lando
Even though we don't look at the chrome value on android in nsLayoutUtils::AreRetainedDisplayListsEnabled(), I flipped it just in case someone looks at that pref somewhere else.
Depends on D25280
Differential Revision: https://phabricator.services.mozilla.com/D25281
--HG--
extra : moz-landing-system : lando
All three failures are small antialiasing differences in the text in the test. The text in the tests aren't even testing anything, they just describe what to expect from the test.
Until we get fuzzy matching in web platform tests (bug 1478472) we just have to mark them as fails, but we can be very specific about the platform, so we're probably still passing these tests on other android jobs if they are run there (not sure).
Differential Revision: https://phabricator.services.mozilla.com/D25280
--HG--
extra : moz-landing-system : lando
Add missing MOZ_SANDBOX preprocessor check before including Sandbox.h to fix the code coverage build.
Remove unused nsMacUtilsImpl.h #include.
Differential Revision: https://phabricator.services.mozilla.com/D25287
--HG--
extra : moz-landing-system : lando
I agree that we should remove PostCSS but since we have contributors moving to MC, I want to get this fixed ASAP.
Differential Revision: https://phabricator.services.mozilla.com/D25258
--HG--
extra : moz-landing-system : lando
