Hello,
I don't know if others on this forum are also experiencing this issue, but since the start of the Firefox ESR 128.5.0-109 package rollout, some of our users have been reporting problems when entering content in the Firefox search bar.
Once the search is entered, it has no effect.
Changing the default search engine (a problem mainly observed with Google) resolves the issue depending on the selected engine.
Resetting the caches or repairing Firefox ESR does not fix the problem.
I'm going to revert to version 128.4.0-109 using a custom package and see if I can report the problem to the Mozilla developers.
Different problems also seem to be reported in discussions on the official Mozilla website:
https://connect.mozilla.org/t5/discussi ... td-p/79615
Thank you in advance.
Fred
[RESOLVED] Problem using the search bar after deploying Firefox ESR package 128.5.0-109
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Frédéric,
indeed the upstream Firefox version seems to have a change in behavior. But since the issue will probably be addressed quickly by Mozilla, I don't think it's relevant to force the change to network.http.http2.allow-push in the wapt package itself.
Otherwise, for those using SSL interception with Firefox version 128.4, you need to force the parameter network.http.http2.allow-push=true in the prefs.json file [1].
I'm marking the topic as RESOLVED.
Best regards,
Denis
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1933747#c4
indeed the upstream Firefox version seems to have a change in behavior. But since the issue will probably be addressed quickly by Mozilla, I don't think it's relevant to force the change to network.http.http2.allow-push in the wapt package itself.
Otherwise, for those using SSL interception with Firefox version 128.4, you need to force the parameter network.http.http2.allow-push=true in the prefs.json file [1].
I'm marking the topic as RESOLVED.
Best regards,
Denis
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1933747#c4
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
