(In reply to Kyle Ferriter from comment #6) > I'm using Nightly on Linux with Mesa driver on an Intel graphics card and webrender is not enabled by default. > > For WEBRENDER_QUALIFIED I get "blocked-screen-too-large by env: Screen size too large". 4K needs further optimizations especially for integrated Intel GPUs: https://mozillagfx.wordpress.com/2019/04/30/webrender-newsletter-44/ > I'm using a 4k display with GNOME Wayland and 2x scaling. This may just be anecdotal but it seems to work fine when I force it with gfx.webrender.all. <3 > Right at startup it's a little wonky and the UI doesn't look right, but after it gets loaded after a few seconds it works well and is smooth. Even without webrender, at startup often the UI is not laid out correctly until I resize the window, forcing it to reevaluate the layouts. That sounds like bug 1502519. I'm seeing it everyday as well.
Bug 1554251 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Kyle Ferriter from comment #6) > I'm using Nightly on Linux with Mesa driver on an Intel graphics card and webrender is not enabled by default. > > For WEBRENDER_QUALIFIED I get "blocked-screen-too-large by env: Screen size too large". 4K needs further optimizations especially for integrated Intel GPUs: https://mozillagfx.wordpress.com/2019/04/30/webrender-newsletter-44/ > I'm using a 4k display with GNOME Wayland and 2x scaling. This may just be anecdotal but it seems to work fine when I force it with gfx.webrender.all. <3 > Right at startup it's a little wonky and the UI doesn't look right, but after it gets loaded after a few seconds it works well and is smooth. Even without webrender, at startup often the UI is not laid out correctly until I resize the window, forcing it to reevaluate the layouts. That sounds like bug 1502519 (or bug 1521175 or any of its not-as-duplicate-marked sisters). I'm seeing it everyday as well.