Temporarily remove javascript.options.main_process_disable_jit #254

Merged

celenity merged 1 commit from any1here/Phoenix:dev into dev

2026-04-12 07:58:29 +02:00

any1here commented

2026-04-03 18:39:25 +02:00

Contributor

https://bugzilla.mozilla.org/show_bug.cgi?id=1992206 somehow ended up breaking translations in 149 when javascript.options.main_process_disable_jit is true

https://bugzilla.mozilla.org/show_bug.cgi?id=1992206 somehow ended up breaking translations in 149 when `javascript.options.main_process_disable_jit` is `true`

degausser commented

2026-04-04 00:15:52 +02:00

First-time contributor

for the record, translations do work for me (on desktop firefox 149) with that pref set to true.

any1here commented

2026-04-04 11:59:54 +02:00

Author

Contributor

@degausser wrote in #254 (comment):

for the record, translations do work for me (on desktop firefox 149) with that pref set to true.

If you read through the Bugzilla, it seems very inconsistent what causes it to break, but toggling that pref fixes it for me.

@degausser wrote in https://codeberg.org/celenity/Phoenix/pulls/254#issuecomment-12626820: > for the record, translations do work for me (on desktop firefox 149) with that pref set to true. If you read through the [Bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=2019140#c31), it seems very inconsistent what causes it to break, but toggling that pref fixes it for me.

celenity referenced this pull request

2026-04-11 06:57:32 +02:00

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

celenity force-pushed dev from 27d094eca4 to e60501f481

2026-04-12 07:54:50 +02:00

Compare

celenity approved these changes

2026-04-12 07:56:01 +02:00

celenity left a comment

LGTM, Thank you!

celenity commented

2026-04-12 07:58:19 +02:00

Owner

I was originally torn on how to handle this, because, like @degausser, I've been unable to replicate the issue - but, after #256, and per discussion there, I think the best course of action is to disable it for now until the upstream bug is fixed. I'll keep it on Phoenix extended though.

I was originally torn on how to handle this, because, like @degausser, I've been unable to replicate the issue - but, after https://codeberg.org/celenity/Phoenix/issues/256, and per discussion there, I think the best course of action is to disable it for now until [the upstream bug](https://bugzilla.mozilla.org/show_bug.cgi?id=2019140) is fixed. I'll keep it on Phoenix `extended` though.

celenity merged commit e60501f481 into dev

2026-04-12 07:58:29 +02:00