After installing this update it is required that you logout of
your current user session and log back in to ensure the changes
supplied by this update are applied properly.
^same behavior with mozilla binaries: default start page focuses, but after setting the start page to the fedoraproject url does not focuse, so upstream issue?
I wish there was a FF build/submit to testing bot for at least patch releases, which probably would not need much in terms of patch/spec rejig. Given how important FF is to everyone, we all want builds the moment Mozilla push the out.
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'waiting'.
Works, fixes VAAPI brighness issue.
Works.
Hm, there's a focus URL bar regression in Fedora package: https://bugzilla.redhat.com/show_bug.cgi?id=2040293
On my system the URL bar is correctly focused at launch, KDE Wayland session
I have home/start page set at blank. If I reset it to https://start.fedoraproject.org, then it does not focuse.
^same behavior with mozilla binaries: default start page focuses, but after setting the start page to the fedoraproject url does not focuse, so upstream issue?
I see the same behaviour as @amdgpu described on my MS-Windows PC at work.
This update has been submitted for testing by stransky.
This update's test gating status has been changed to 'failed'.
Okay, doesn't look like a bug then.
Infinite loop in HTTP3 hangs socket thread
@xvitaly That was fixed, and it's not specific to this version.
Re-thumbing just in case
It looks like, the HTTP/3 issue was fixed on Mozilla's side.
This update's test gating status has been changed to 'passed'.
The Theora format link at https://fedoraproject.org/wiki/QA:Testcase_firefox_media is dead, can someone find a good live replacement?
This update has been submitted for stable by bodhi.
Never mind, I found an updated link to what are probably the same videos.
This update has been pushed to stable.
Is 96.0.1 going be be build as well or was https://bugzilla.mozilla.org/show_bug.cgi?id=1749957 already included in 96 build?
@markec: I do not see any mention of that particular bug being fixed in the 96.0 spec file, so we'll probably have to wait for 96.0.1.
Yeah, someone needs to kick of builds on Koji I reckon?
We have 96.0.2 out as well now :)
I wish there was a FF build/submit to testing bot for at least patch releases, which probably would not need much in terms of patch/spec rejig. Given how important FF is to everyone, we all want builds the moment Mozilla push the out.
I can see 96.0.1 was build but no pushed. and 96.0.2 wasn't started yet. Is there anything blocking builds of FF ATM?
Is this being worked on or is it blocked?
Yeah, no builds for 96.0.2 yet. Given there is 96.0.3 candidate now, there is probably no point building .2 anymore.
Indeed! Seems we still don;'t have builds? Is there anyone around that can trigger those? :)