As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, post in the support forum instead pls :))
Tomorrow, August 6, is the release day for Firefox 129.
These links will contain the usual bits of information for the new version once the release is live:
* release notes: https://www.mozilla.org/firefox/129.0/releasenotes/
* sec advisories: [https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox129]
* complete list of changes: [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=target_milestone&o3=equals&v3=Firefox%20129&o1=equals&resolution=FIXED&o2=anyexact&query_format=advanced&f3=target_milestone&f2=cf_status_firefox129&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&v1=mozilla129&v2=fixed%2Cverified&limit=0]
* developer notes: [https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/129]
As always feel free to add to this thread if you see other news or common problems popping up with the release as it goes live to more users. If you're a user yourself looking for help though, [https://support.mozilla.org/questions/new post in the support forum instead] pls :))
HTTPS is replacing HTTP as the default protocol in the address bar on non-local sites. If a site is not available via HTTPS, Firefox will fall back to HTTP.
This could lead to more reports of secure connection errors where the user needs to manually edit the protocol as a workaround, but we'll have to wait and see how "smart" the fallback is.
This is in the release notes is interesting:
<blockquote>HTTPS is replacing HTTP as the default protocol in the address bar on non-local sites. If a site is not available via HTTPS, Firefox will fall back to HTTP.</blockquote>
This could lead to more reports of secure connection errors where the user needs to manually edit the protocol as a workaround, but we'll have to wait and see how "smart" the fallback is.
I added a couple of incidents in our release wiki for Firefox 129. There's one desktop incident that caused Hulu playback to fail for some content (bug1911283).
Hi folks,
I added a couple of incidents in our release wiki for Firefox 129. There's one desktop incident that caused Hulu playback to fail for some content ([https://bugzilla.mozilla.org/show_bug.cgi?id=1911283 bug1911283]).
Under certain conditions, copyrighted video served via digital rights management may experience playback issues.
A patch is underway. For an immediate workaround, please complete the following steps:
Go to about:config in the Awesomebar.
Search for media.eme.mfcdm.origin-filter.enabled.
Flip the pref from 1 to 0.
Select the check mark button.
I have tagged questions see with '''bug1911283'''
The suggested response is:
*****
Hi
Under certain conditions, copyrighted video served via digital rights management may experience playback issues.
A patch is underway. For an immediate workaround, please complete the following steps:
# Go to about:config in the Awesomebar.
# Search for media.eme.mfcdm.origin-filter.enabled.
# Flip the pref from 1 to 0.
# Select the check mark button.
*****
Fixed
Fixed playback issues on some websites with copyrighted video served via digital rights management. (Bug 1911283)
Fixed a crash when dragging a video file onto some websites. (Bug 1910990)
Firefox 129.0.1 is Released.
https://www.mozilla.org/firefox/129.0.1/releasenotes/
<blockquote>Fixed
Fixed playback issues on some websites with copyrighted video served via digital rights management. (Bug 1911283)
Fixed a crash when dragging a video file onto some websites. (Bug 1910990)</blockquote>
Multiple reports like this one claim that there's issue with searching from either the address bar or the Google search bar. After hitting return nothing happens.
Does anyone knows what's going on there?
Multiple reports like [https://support.mozilla.org/en-US/questions/1458528 this one] claim that there's issue with searching from either the address bar or the Google search bar. After hitting return nothing happens.
Does anyone knows what's going on there?
Multiple reports like this one claim that there's issue with searching from either the address bar or the Google search bar. After hitting return nothing happens.
Does anyone knows what's going on there?
I replied asking what they use for their home page.
There is a longstanding bug related to some pages that Firefox cannot navigate away from using the address bar. It's marked security-sensitive. If there's a particular website that causes this when set as a user's home page, that bug needs more attention.
''TyDraniu [[#post-87982|said]]''
<blockquote>
Multiple reports like [https://support.mozilla.org/en-US/questions/1458528 this one] claim that there's issue with searching from either the address bar or the Google search bar. After hitting return nothing happens.
Does anyone knows what's going on there?
</blockquote>
I replied asking what they use for their home page.
There is a longstanding bug related to some pages that Firefox cannot navigate away from using the address bar. It's marked security-sensitive. If there's a particular website that causes this when set as a user's home page, that bug needs more attention.
Fixed
Fixed an issue with screen readers prompting "Alert" when hovering over tabs. (Bug 1908873)
Fixed an issue where drag-and-drop operations would not work as expected with extensions that rely on this functionality. (Bug 1911486)
Firefox 129.0.2 is released.
https://www.mozilla.org/firefox/129.0.2/releasenotes/
<blockquote>Fixed
Fixed an issue with screen readers prompting "Alert" when hovering over tabs. (Bug 1908873)
Fixed an issue where drag-and-drop operations would not work as expected with extensions that rely on this functionality. (Bug 1911486)</blockquote>
I have heard that there is a perf issue with YT on ESR 115 - this is a YT problem and they are fixing it. Not too worried about tracking questions at this time as it may have been fixed by now (or is not far off).
I have heard that there is a perf issue with YT on ESR 115 - this is a YT problem and they are fixing it. Not too worried about tracking questions at this time as it may have been fixed by now (or is not far off).
The current live version of ESR is 115.14, with 115.15 heralding the switchover to 128 on the 3rd September, but with support for 115 being retained for Win 7 & 8 for a while yet. Slack is removing support for ESR 115 on the 1st of September.
I believe efforts are being made to resolve this, but just be aware that those not on Win7 or 8 may be best advised to either manually move to 128 or wait for the update on the 3rd if they report issues with Slack.
The current live version of ESR is 115.14, with 115.15 heralding the switchover to 128 on the 3rd September, but with support for 115 being retained for Win 7 & 8 for a while yet. Slack is removing support for ESR 115 on the 1st of September.
I believe efforts are being made to resolve this, but just be aware that those not on Win7 or 8 may be best advised to either manually move to 128 or wait for the update on the 3rd if they report issues with Slack.
The current live version of ESR is 115.14, with 115.15 heralding the switchover to 128 on the 3rd September, but with support for 115 being retained for Win 7 & 8 for a while yet. Slack is removing support for ESR 115 on the 1st of September.
Hmm, I see they say "The support cycle for Firefox follows Mozilla's Rapid Release schedule and excludes the Extended Support Release (ESR) schedule." (ref)
Maybe a user agent switcher (or network.http.useragent.forceVersion) can work around it temporarily if Win7 users don't have another option.
''Paul [[#post-88024|said]]''
<blockquote>
The current live version of ESR is 115.14, with 115.15 heralding the switchover to 128 on the 3rd September, but with support for 115 being retained for Win 7 & 8 for a while yet. Slack is removing support for ESR 115 on the 1st of September.
</blockquote>
Hmm, I see they say "The support cycle for Firefox follows Mozilla's Rapid Release schedule and excludes the Extended Support Release (ESR) schedule." ([https://slack.com/help/articles/1500001836081-Slack-support-lifecycle-for-operating-systems-app-versions-and-browsers ref])
Maybe a user agent switcher (or network.http.useragent.forceVersion) can work around it temporarily if Win7 users don't have another option.
