Originally posted by uid313
View Post
Announcement
Collapse
No announcement yet.
Firefox 78.0 Released - Also Serves As The Newest ESR Version
Collapse
X
-
Originally posted by frank007To reiterate: They don't want!
- Likes 7
Comment
-
Originally posted by frank007
To reiterate: They don't want!
- Likes 2
Comment
-
Originally posted by bug77 View Post
Man, I really thought you'd stop whining after Firefox implemented date and time pickers. Joke's on me, I guess.
Firefox still does not support input type "week", "month" and "datetime-local". 😢
- Likes 1
Comment
-
Originally posted by uid313 View Post
It took crazy long time for Firefox to implement date and time pickers. I love Firefox but sometimes it feels like the new Internet Explorer.
Firefox still does not support input type "week", "month" and "datetime-local". 😢
Comment
-
Originally posted by treba View Post
See https://mastransky.wordpress.com/202...pi-on-wayland/ - you need a bit more atm.
Comment
-
Originally posted by caligula View Post
I tried all the steps and forced Youtube to deliver h264 video. Basically the only missing step was, I had not force enabled DMABUF. Now I did that. On Gnome3/Wayland the Firefox process shows 30% load on all cores and around 70% under a single Firefox process in top. The load increases if there's some floating advertisement on top of the video layer or if some other window is drawn on top of Firefox window's video canvas. The vainfo output seems almost identical to the one shown in the article.
1: https://bugzilla.mozilla.org/show_bug.cgi?id=1648799
2: https://bugzilla.mozilla.org/show_bu...id=1625070#c13
- Likes 1
Comment
-
Originally posted by treba View PostAFAIK the main problem is DMABUF.
More than that, there is a patchset in the Bugzilla which implements VA-API decoding to X Drawables. The same approach can be used for VDPAU too.
This is how PepperFlash adapter handled hw decoding, and it worked for both VA-API and VDPAU, so I have my words backed up.
Originally posted by treba View Postsomething they tried but disabled as it was found to be bug prone on nvidia (1).
So if they were using APIs incorrectly in Firefox and it worked, and then a newer driver version made it stop working, it's not a driver fault if it's still obeys specifications.
- Likes 1
Comment
Comment