Originally posted by brent
View Post
Announcement
Collapse
No announcement yet.
Firefox 75 On Wayland Now To Have Full WebGL, Working VA-API Acceleration
Collapse
X
-
Originally posted by brent View Post
- Likes 15
Comment
-
Originally posted by frank007 View PostIt would be interesting to see some benchmark between the Firefox/Chromium solution and the real hardware decoding (vlc, mplayer, mpv, etc.).
When did Firefox officially support Wayland?
Why didn't they start with supporting X.org? I couldn't care less about Wayland which is still largely a tech demo.
- Likes 21
Comment
-
Originally posted by TemplarGR View Post
Unusable? No. You are overreacting. I have been using Firefox 73 on Wayland for many days and while it gets annoying sometimes, it is far, far from unusable.
BTW, the problem doesn't exist on GNOME 3.34.x, only on 3.35/3.36 or on 3.34 with specific performance-enhancing patches. GNOME introduced more efficient culling of redundant surfaces updates, and Firefox does not handle that correctly yet.Last edited by brent; 03 March 2020, 10:01 AM.
- Likes 1
Comment
-
Originally posted by brent View Post
Unfortunately not. The browser isn't really usable if you can't properly interact with it with the mouse. It's not just the hover effect that's broken, there's more to this issue. But even a broken hover effect alone makes it very irritating to use. I quickly downgraded to Firefox 72 after encountering the problem.
BTW, the problem doesn't exist on GNOME 3.34.x, only on 3.35/3.36 or on 3.34 with specific performance-enhancing patches. GNOME introduced more efficient culling of redundant surfaces updates, and Firefox does not handle that correctly yet.
- Likes 5
Comment
-
Originally posted by GrayShade View PostFor anyone who wants to try this, it's only enabled for H.264. Use the h264ify add-on to for that if you want to test on YouTube.## VGA ##
AMD: X1950XTX, HD3870, HD5870
Intel: GMA45, HD3000 (Core i5 2500K)
- Likes 3
Comment
-
Originally posted by darkbasic View Post
Most of the youtube videos don't get encoded with h.264 anymore, so chances are most of them won't work. Why only H.264? It's kind of stupid...
- Likes 11
Comment
-
Originally posted by TemplarGR View Post
Dude, stop spreading FUD. I have been using Firefox on Wayland heavily these days, and i have no issue whatsoever completing my work. What are you talking about? Yes, links don't get visibly highlighted (but are still clickable normally), sometimes you need to clik inside a frame in order to pass control to it (instead of gettin the focus automatically) plus sometimes the switch of focus is mistakenly placed, but other than that Firefox is production ready as it is. You are just a drama queen. "Not usable" means people can't use it. Well, people can use Firefox today on Wayland just fine. It is just an annoying bug that will get fixed soon.
- Likes 1
Comment
-
Originally posted by Britoid View PostPartially the same if they're using vaapi, but Firefox is taking it an extra step and using dmabuf which doesn't work under X and avoids copying around pixels. This would also have the advantage of letting you eventually use hardware planes dedicated for video.
mpv uses VAAPI in the exact same way under X and Wayland and there's no copies being done either way. It's very simple - grab hardware surface handle using vaExportSurfaceHandle(), import surface data into OpenGL using EGL_EXT_image_dma_buf_import. mpv does exactly that, and it doesn't matter if it's under X or Wayland. If Firefox can't do that in X, that's a Firefox limitation, not something inherent in X.
- Likes 7
Comment
Comment