Intent to prototype and ship: running background color animations on the compositor thread
Summary: According to a Chrome Platform Status statistics site [1] `background-color` is the third most popular animating CSS property. Running background color animations on the compositor makes the main thread less busy because styling/painting for the animations are skipped on the main thread. Which means that it improves performance and reduces battery consumption theoretically. Bugs: for WebRender https://bugzilla.mozilla.org/show_bug.cgi?id=1510030 for non WebRender https://bugzilla.mozilla.org/show_bug.cgi?id=1504065 As you may know, on our Nightlies it's been enabled since Nov. 2018 for non WebRender backend. The WebRender backend will be landed soon. Platform coverage: all Preference: gfx.omta.background-color DevTools bug: There is no specific bugs for devtools because the animation inspector has already a feature which shows a lightning bolt icon for each animation if the animation runs on the compositor. See a document [2] for details. Other browsers: No other browser implements it, as far as I know. A few years ago, Chrome seems to start considering it [3], but I don't know what the current status is. As a side note, Blink plans to run clip-path animations on the compositor [4], WebKit is interested in it [5] (Though I've heard WebKit has already implemented it, I may be mis-remembering). We might plan to do it at some point in future. Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1535532 Target Release: 76 hiro [1] https://www.chromestatus.com/metrics/css/animated [2] https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Work_with_animations#Animation_inspector [3] https://groups.google.com/a/chromium.org/d/msg/paint-dev/3-_82v7-tK8/LNkGN0ywBQAJ [4] https://bugs.chromium.org/p/chromium/issues/detail?id=686074 [5] https://bugs.webkit.org/show_bug.cgi?id=185816 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to prototype and ship: lazy load images
On Sat, Feb 15, 2020 at 4:48 AM Boris Zbarsky wrote: > On 2/6/20 5:26 PM, Hiroyuki Birchill Ikezoe wrote: > > Is this feature enabled by default in sandboxed iframes?: no, as of now > > there is no proposed flag to enable this feature in sandboxed iframes. > > But is it disabled by default there? I would assume not, unless it's > specifically gated on sandboxing state... > To be more precise, lazy loading is disabled in documents where scripting is disabled. Though I don't know the exact conditions where scripting is disabled, by default lazy loading is disabled without `allow-scripts` keyword. hiro ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to Unship: in content
One caveat I should mention is that mobile viewport stuff (which is used in RDM as well) relies on the fact that Document::IsTopLevelContentDocument returns true. The function actually returns true for the document of ``. So please make sure it still returns true for the replacement or add an equivalent function. hiro On Sat, Feb 15, 2020 at 4:48 AM Patrick Brosset wrote: > Thanks Kris. > > Related to this: RDM (Responsive Design Mode, in DevTools) is one of the > consumers of . We've been at work removing the > dependency from RDM on this type of iframe, and are nearing the completion > of the main bucket of work. By March this year, we should have a new, fully > functional version of RDM that does not depend on . > The "old" RDM will still be in the tree by this date and we might not have > pref'd the new one on yet, but we'll be very close. > > A simple completion chart for this project can be found at > https://arewefissionyet.com/devtools/ (under the RDM section). > In bugzilla, the whiteboard flag fission-rdm-mvp tracks the project: > > https://bugzilla.mozilla.org/buglist.cgi?quicksearch=fission-rdm-mvp_id=15103084 > > Patrick > > On Mon, Feb 10, 2020 at 9:46 PM Kris Maglione > wrote: > > > in non-chrome documents has been unsupported > > in production environments for some time. Maintaining support > > for it in content processes has become increasingly difficult in > > the light of Fission, to the point that we've decided it is time > > to fully remove support. Since support is disabled by default, > > and there is no user-visible way to enable it, there should be > > no users in the wild. The only in-tree users are tests, which > > will need to be updated by their owners or disabled. > > > > Bug 1614462 will track this work. > > > > > > -Kris > > ___ > > firefox-dev mailing list > > firefox-...@mozilla.org > > https://mail.mozilla.org/listinfo/firefox-dev > > > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to prototype and ship: lazy load images
On Tue, Feb 11, 2020 at 12:43 AM Anne van Kesteren wrote: > On Mon, Feb 10, 2020 at 3:22 PM Hiroyuki Birchill Ikezoe > wrote: > > Is this feature enabled by default in sandboxed iframes?: no, as of now > > there is no proposed flag to enable this feature in sandboxed iframes. > > I think the answer to this question is more complicated. It's disabled > if scripts are disabled, but if scripts are enabled, image lazy load > is enabled, right? > Right. Thanks for the clarification. hiro ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Intent to prototype and ship: lazy load images
In Firefox 75, I intend to turn lazy load images on by default. Summary: lazy load images improves initial page load performance by deferring loading images which are out of viewport, it also reduces network traffic. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1542784 Standard: https://github.com/whatwg/html/pull/3752 Platform coverage: all Preference: dom.image-lazy-loading.enabled Devtools bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1611387 Other browsers: Chrome has shipped it since 76. WebKit is now implementing it [1] web-platform-tests: https://wpt.fyi/results/loading/lazyload?label=experimental=master Secure contexts: this feature is not restricted to secure contexts. I don't see any reasons to restrict it in secure contexts. If you have concerns, please let me know. Is this feature enabled by default in sandboxed iframes?: no, as of now there is no proposed flag to enable this feature in sandboxed iframes. Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1613611 hiro [1] https://bugs.webkit.org/show_bug.cgi?id=200764 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
