just asking wouldn't porting firefox to qt solve this issue?
Announcement
Collapse
No announcement yet.
Firefox Wayland By Default Diverted To Fedora 31
Collapse
X
-
Originally posted by Kayote View Postjust asking wouldn't porting firefox to qt solve this issue?
- Likes 1
Comment
-
Originally posted by Kayote View Postjust asking wouldn't porting firefox to qt solve this issue?
Overall progress of Firefox on Linux feels quite slow. For instance hardware accelerated video encoding / decoding is missing for years and nobody seems to be working on it. This makes for example using Firefox with WebRTC on weaker laptops close to impossible due to CPU bottlenecking. I'm saying it as a long time Firefox user who doesn't use Chromium.Last edited by shmerl; 19 March 2019, 12:14 AM.
- Likes 1
Comment
-
Originally posted by Anvil View Post
from Thunderbird68 an firtefox68 will all have much better support for Wayland. current ESR of TB is Crap
Code:Compositing OpenGL GPU #1 Active Yes Description X.Org -- AMD RAVEN (DRM 3.27.0, 4.20.15-200.fc29.x86_64, LLVM 7.0.1) Vendor ID X.Org Device ID AMD RAVEN (DRM 3.27.0, 4.20.15-200.fc29.x86_64, LLVM 7.0.1) Driver Version 4.5 (Compatibility Profile) Mesa 18.3.4
Last edited by finalzone; 19 March 2019, 12:21 AM.
- Likes 2
Comment
-
Originally posted by shmerl View Post
It would make things better overall. GTK is just a mess. That's not Wayland specific. I suppose Firefox developers are so insistent on using GTK and even let already existing Qt Firefox branch die out, due to RedHat being heavy backers of Gnome and one of the major sponsors of Firefox Linux development. Since they are focused on GTK, Firefox tags along
Overall progress of Firefox on Linux feels quite slow.
In fact if you compare the screenshot from 2018 here
- https://i0.wp.com/fosspost.org/wp-co...50%2C392&ssl=1
and
- https://wiki.xfce.org/releng/4.14/roadmap
you'll see that xfce4-session has regressed backwards. From 100% to 99%. No progress on xfwm4 in over a year.
Also GTK3 GIMP is still WIP even though GIMP started the whole GTK. GIMP developers have probably the best knowledge of GTK on this planet. So how can it take so long?
For instance hardware accelerated video encoding / decoding is missing for years and nobody seems to be working on it. This makes for example using Firefox with WebRTC on weaker laptops close to impossible due to CPU bottlenecking. I'm saying it as a long time Firefox user who doesn't use Chromium.
Comment
-
Originally posted by finalzone View Post
Using Thunderbird-Wayland and Firefox-Wayland on daily basis with default setting. Only issue is when enabling OpenGL compositing on some systems. So far, both Thunderbird and Firefox on Wayland run smoothly on AMD Ryzen 2500u using latest stable amdgpu driver.
Code:Compositing OpenGL GPU #1 Active Yes Description X.Org -- AMD RAVEN (DRM 3.27.0, 4.20.15-200.fc29.x86_64, LLVM 7.0.1) Vendor ID X.Org Device ID AMD RAVEN (DRM 3.27.0, 4.20.15-200.fc29.x86_64, LLVM 7.0.1) Driver Version 4.5 (Compatibility Profile) Mesa 18.3.4
Comment
-
Originally posted by caligula View PostIsn't that related to Wayland? It's not possible to optimize the video decoding and overlays before Wayland is available?
Comment
-
Originally posted by finalzone View Post
Using Thunderbird-Wayland and Firefox-Wayland on daily basis with default setting. Only issue is when enabling OpenGL compositing on some systems. So far, both Thunderbird and Firefox on Wayland run smoothly on AMD Ryzen 2500u using latest stable amdgpu driver.
Code:Compositing OpenGL GPU #1 Active Yes Description X.Org -- AMD RAVEN (DRM 3.27.0, 4.20.15-200.fc29.x86_64, LLVM 7.0.1) Vendor ID X.Org Device ID AMD RAVEN (DRM 3.27.0, 4.20.15-200.fc29.x86_64, LLVM 7.0.1) Driver Version 4.5 (Compatibility Profile) Mesa 18.3.4
Comment
-
Originally posted by shmerl View Post
It would make things better overall. GTK is just a mess. That's not Wayland specific. I suppose Firefox developers are so insistent on using GTK and even let already existing Qt Firefox branch die out, due to RedHat being heavy backers of Gnome and one of the major sponsors of Firefox Linux development. Since they are focused on GTK, Firefox tags along
Overall progress of Firefox on Linux feels quite slow. For instance hardware accelerated video encoding / decoding is missing for years and nobody seems to be working on it. This makes for example using Firefox with WebRTC on weaker laptops close to impossible due to CPU bottlenecking. I'm saying it as a long time Firefox user who doesn't use Chromium.
Comment
-
Originally posted by tildearrowuid will be sad...
I tried Firefox nightly under Wayland, it works, but it have some bugs involving shadow on menus.
Originally posted by Vasant1234 View PostIt is not just Firefox, Thunderbird and LibreOffice suite also need to support Wayland. In other words give it another 5 years.
Originally posted by Charlie68 View PostI ask those who have expertise in the matter, it's so complicated to bring an application from Xorg to native Wayland ?
If it a simple or complex application that implements its own way of doing things and directly does X11 calls.
I coded a GTK application using Python and it works great in both X and Wayland. There is no X-specific or Wayland-specific code. It is just GTK calls.
Originally posted by horizonbrave View Postshouldn't Gnome Web be the default browser on the default Gnome Desktop distro?
So some distributions can chose to ship the GNOME desktop with GNOME Web, others are free to ship a GNOME-based distribution with Firefox or Chromium.
Originally posted by Aeder View PostNot surprising. When this was first announced I mentioned that the bug tracker was still full of bugs blocking wayland (40+). It remains full of bugs.
I don't think announcing you want to do something is magically going to get all the roadblocks to disappear.
What to consider is not only the amount of bugs, but the significance of the bugs, i.e. which bugs are minor and which are blocking.NEW (stransky) in Core - Graphics. Last updated 2019-03-18.
- Likes 1
Comment
Comment