Originally posted by uid313
View Post
Announcement
Collapse
No announcement yet.
Firefox 78.0 Released - Also Serves As The Newest ESR Version
Collapse
X
-
- Likes 1
-
Originally posted by caligula View PostNot sure what I'm missing, but I tried watching a H264 1080p video via Youtube/FF78. Don't see much difference in CPU utilization when using Wayland or X11. The CPU use is rather high, up to 30%. My setup:
- kernel 5.7.6
- mesa 20.1.2
- gnome 3.36 (start in x11/wayland mode via gdm)
- skylake notebook igpu
- firefox 78
Yes, I forced webrender stuff on.
- Likes 1
Leave a comment:
-
Not sure what I'm missing, but I tried watching a H264 1080p video via Youtube/FF78. Don't see much difference in CPU utilization when using Wayland or X11. The CPU use is rather high, up to 30%. My setup:
- kernel 5.7.6
- mesa 20.1.2
- gnome 3.36 (start in x11/wayland mode via gdm)
- skylake notebook igpu
- firefox 78
Yes, I forced webrender stuff on.
Leave a comment:
-
Originally posted by frank007You are in the wrong path. It can be done also for Xorg without any problems. They simply don't want! My question is: Why?
Edit: a good video player would do the same IMO. Videos are often from untrusted sources - decoding them without proper isolation, well, see https://www.vice.com/en_us/article/v...ster-hernandezLast edited by treba; 30 June 2020, 04:23 PM.
- Likes 4
Leave a comment:
-
I don't know about that. dom.dialog_element.enabled is still false on my system running nightly and is marked as default false.
So it seems it is still not supported. I don't know why it has taken them this so long, it seems like a good feature to have a semantic markup for dialogs, that would be good for like robots, search engines, accessibility, screen readers, etc.
Oh, it got reverted from nightly.
Hopefully it will be fixed soon and maybe pushed again tomorrow or very soon. I wish they had this feature a year ago.
Leave a comment:
-
I think there should be a rule where you cannot complain about any OSS when using nVidia. it almost always invalidates anything that has been said.
- Likes 9
Leave a comment:
-
Guest
Just use the VAAPI-vdpau bridge (libva-vdpau-driver) if you must use VDPAU. You may need to disable the built-in ffmpeg (licensing reasons) via media.ffvpx.enabled:false in addition to that. Note that there's already the first crash reported in NVIDIAs vdpau_drv_video.so.
Originally posted by frank007There is no will !
uid313 HTML5 Dialog just landed in Nightly.
- Likes 5
Leave a comment:
-
Overall a great browser.
Just too bad a few things are missing:- Dialog element
- system-ui font-family
- Private class fields
Leave a comment:
-
Originally posted by frank007
Well, I've just made some tests. My ffmpeg is linked with libvdpau, but ffplay cannot use it (in fact, there is no video engine utilization). ffplay can use the decoder h264_cuvid (command line: ffplay -vcodec h264_cuvid FILE.mp4). The absurd thing is I can decode, using cuvid, also other vdpau unsupported video files via hardware. I always checked the Video Engine Utilization from Nvidia Settings.
So, there is no reasons not to implement hardware acceleration using the vdpau interface in Firefox, Chrome, Chormium(s) and whatever browsers will make tomorrow. There is no will !
The video engine utilization and the gpu and the cpu is not the same using vdpau or cuvid.
So well, the easiest would probably be if nvidia would simply allow their firmware to be shipped with free drivers - just as other good linux citizens do
1: https://searchfox.org/mozilla-centra...List.yaml#4179Last edited by treba; 30 June 2020, 12:49 PM.
- Likes 7
Leave a comment:
Leave a comment: