[BUG] AI settings unavailability adversely affects all translation function across all sites. #256

GW72 commented 2026年04月07日 15:24:20 +02:00

Confirmation Checklist

• I confirm that this issue occurs on the latest release of Phoenix. You can check what the latest version is on the Releases page.
• I confirm that this issue has NOT already been reported on the Codeberg issue tracker, the GitLab issue tracker, and/or the GitHub issue tracker.

What web browser(s) are you using with Phoenix?

Firefox

Other

No response

What operating system(s) are you experiencing this issue on?

No response

Other

ubuntu 24.04

What version of Firefox/Gecko and Phoenix are you using?

FF 149.0.2
Phoenix 2026年03月31日.1

If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on?

No response

Does the issue occur on a new browser profile?

• Yes
• No

Please share your browser's distribution ID.

default

Please share your browser's update channel.

https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/noble main

Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed.

uBO
trocker
LocalCDN
NewTab - redirect
Sponsorblock
FF containers

Please explain the issue you are experiencing.

The AI section in settings is absent. As translations are now controlled by AI settings, and now translations do not function, I would like to be able to access AI settings.

Please provide detailed steps to reproduce the issue.

Translation function is unavailable at all times, for any website. I need translations to be available. I need AI settings to be available in order to access translation function, and whatever related settings to be undone such that language translations function properly.

### Confirmation Checklist - [x] I confirm that this issue occurs on the **latest release** of Phoenix. You can check what the latest version is on [the `Releases` page](https://codeberg.org/celenity/Phoenix/releases). - [x] I confirm that this issue has **NOT** already been reported on [the Codeberg issue tracker](https://codeberg.org/celenity/Phoenix/issues), [the GitLab issue tracker](https://gitlab.com/celenityy/Phoenix/-/issues), **and/or** [the GitHub issue tracker](https://github.com/celenityy/Phoenix/issues). ### What web browser(s) are you using with Phoenix? Firefox ### Other _No response_ ### What operating system(s) are you experiencing this issue on? _No response_ ### Other ubuntu 24.04 ### What version of Firefox/Gecko and Phoenix are you using? FF 149.0.2 Phoenix 2026年03月31日.1 ### If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on? _No response_ ### Does the issue occur on a new browser profile? - [x] Yes - [ ] No ### Please share your browser's distribution ID. default ### Please share your browser's update channel. https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/noble main ### Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed. uBO trocker LocalCDN NewTab - redirect Sponsorblock FF containers ### Please explain the issue you are experiencing. The AI section in settings is absent. As translations are now controlled by AI settings, and now translations do not function, I would like to be able to access AI settings. ### Please provide detailed steps to reproduce the issue. Translation function is unavailable at all times, for any website. I need translations to be available. I need AI settings to be available in order to access translation function, and whatever related settings to be undone such that language translations function properly.

celenity commented 2026年04月11日 06:57:32 +02:00

@GW72 Hey, thanks for the report. We definitely support Translations, and in fact, we go out of our way to explicitly enable it with the new AI pref (browser.ai.control.translations). Translations should work regardless of whether the AI setting panel is enabled, but you can re-enable it if desired by setting browser.ai.control.translations to true - though that shouldn't make a difference.

If possible, can you please try setting javascript.options.main_process_disable_jit to false, and restarting the browser? Apparently, according to #254, that pref can cause issues with Translations - though I haven't been able to replicate them in testing. If that pref does it fix for you, please LMK, because I'll probably disable it by default if it does.

Sorry to hear you're still having trouble with Translations after all this time... I guess it just hates you personally for some reason :P.

@GW72 Hey, thanks for the report. We definitely support Translations, and in fact, we go out of our way to explicitly enable it with the new AI pref *(`browser.ai.control.translations`)*. Translations should work regardless of whether the AI setting panel is enabled, but you can re-enable it if desired by setting `browser.ai.control.translations` to `true` - though that shouldn't make a difference. If possible, can you please try setting `javascript.options.main_process_disable_jit` to `false`, and restarting the browser? Apparently, according to https://codeberg.org/celenity/Phoenix/pulls/254, that pref can cause issues with Translations - though I haven't been able to replicate them in testing. If that pref does it fix for you, please LMK, because I'll probably disable it by default if it does. Sorry to hear you're still having trouble with Translations after all this time... I guess it just hates you personally for some reason :P.

GW72 commented 2026年04月12日 05:36:15 +02:00

@celenity thanks for the solution, which was to set to false the config javascript.options.main_process_disable_jit. I can add that for the same version of phoenix on windows 11 25H2, translations continued to work as normal without interventions on FF 149. Other than this curse of translation roulette on ubuntu, phoenix works flawlessly and I am grateful for all your efforts.

Checking with grok it seems this config set to false does (at least currently with FF 149) not seem to impart any huge extra security risk or concerns at least until the next iteration of something like CVE-2019-11707 + IPC logic bug comes around. Perhaps it would be more appropriate for inclusion in the extended hardening option?

@celenity thanks for the solution, which was to set to `false` the config `javascript.options.main_process_disable_jit`. I can add that for the same version of `phoenix` on `windows 11 25H2`, translations continued to work as normal without interventions on FF 149. Other than this curse of translation roulette on ubuntu, `phoenix` works flawlessly and I am grateful for all your efforts. Checking with `grok` it seems this `config` set to `false` does (at least currently with FF 149) not seem to impart any huge extra security risk or concerns at least until the next iteration of something like `CVE-2019-11707 + IPC logic bug `comes around. Perhaps it would be more appropriate for inclusion in the `extended hardening` option?

celenity commented 2026年04月12日 07:49:25 +02:00

@GW72 Thank you for confirming!

Perhaps it would be more appropriate for inclusion in the extended hardening option?

There actually is an upstream bug about this, but, until it's fixed - yes, I agree this is the best course of action. Will be done for next release, thanks again for your time and support! :)

@GW72 Thank you for confirming! > Perhaps it would be more appropriate for inclusion in the `extended hardening` option? There actually is an [upstream bug about this](https://bugzilla.mozilla.org/show_bug.cgi?id=2019140), but, until it's fixed - yes, I agree this is the best course of action. Will be done for next release, thanks again for your time and support! :)