Repository navigation
[BUG] 149.0.2 and later. The "Page Info" window does not work properly after installing a language pack. #239
Description
Browser (please complete the following information):
- OS: [Any]
- Version: [r3dfox v149.0.2 for Vista+]
- This is a r3dfox specific bug: [Verified: There is no issue in Firefox by e3kskoy7wqk.]
Describe the bug
After installing a language pack from Firefox, the "Page Info" window (Ctrl+I) does not work properly: the “Media” section is missing, and the "Permissions" and "Security" sections are empty. The language does not matter, the issue occurs with any installed language pack. Tested in Russian, German, Belarusian, French, Spanish, English (UK), and Japanese.
To Reproduce
Steps to reproduce the behavior:
- Install any interface language under General - Language.
- Restart your browser.
- Open any website (the "Media" section appears on the browser's internal pages).
- Press Ctrl+I to open the window.
- There won't be a "Media" section, and "Permissions" and "Security" don't work.
Screenshots
It should be like this:
Additional context
The bug first appeared in version 149.0.2 and is still present in version 153.0-hotfix. The bug is not present in beta version r3dfox beta b149.0 for Vista+. Version ESR 140.11.0 has no bugs.
Activity
Vangelis66 commentedon Aug 1, 2026
The
Page Infobreakage after a non-en-US(Firefox) locale has been installed and enabled was first reported back in early May:#168
then again a duplicate report appeared in mid-May:
#172
This bug came as a result of the increasing LibreWolf-ification of
r3dfox(inclusion of a growing chunk/number of LW code/features), in a way that rendered the official Mozilla Firefox localisation packs (partly) incompatible with the hybrid (officialFirefox+r3dfoxown code+LWcode) that ther3dfoxfork has now become 😞 ...The author is not inclined or able to address this localisation breakage (after all, it's their browser and they're from the USA, no need for them to localise it differently 😉 ), so the issue will probably get worse with time...
TL;DR: This is a duplicate.
Vangelis66 commentedon Aug 2, 2026
Also, it's worth noting that as soon as you download/install a new langpack (other than the default,
en-US) and select/enable the new locale (elorΕλληνικάin my case), thePageInfowindow works localised (with some non-localised strings in thePermissionstab) for as long as you DON'T restart the browser:multimedia tab
permissions tab
security tab
But AFTER a browser restart (recommended when changing locales), the
PageInfowindow becomes BROKEN as per first post...K4sum1 commentedon Aug 2, 2026
Known issue, been reported before. Not sure what to do about it exactly. However the name for this issue is more accurate than the existing one so I'll close the old issue as a duplicate of this.
EDSln commentedon Aug 2, 2026
I'll try comparing the built-in language pack with the one from Firefox. Most likely, it's missing some strings, which is causing the window to malfunction.
K4sum1 commentedon Aug 2, 2026
Yeah it relates to the Librewolf changes not having localizations. Maybe could hardcode it idk. I'd almost rather completely remove language packs and the backend shit for it as it feels like a ton of bloat but I'd have to do that for every version and that sounds like hell.
EDSln commentedon Aug 2, 2026
I found the cause and solution for the "Page Info" window not working. The problem was caused by the "Create WebGL context" setting added via LibreWolf. To fix this, open the language pack file in 7-Zip or rename the file extension to .zip and open it with any archiver, then navigate to the folder \browser\chrome\ru\locale\browser\ (replace “ru” with your language), find the file “sitePermissions.properties” there, extract it, open it in Notepad, and add the line
permission.webgl.label = Create WebGL contextat the end. I didn’t translate it since it’s clear enough what it means, and I have WebGL enabled for everyone, so I don’t need this setting. Save the file, replace the file in the archive with it, restore the .xpi extension, and install the language pack. If it’s already installed, first uninstall the existing one and then install the new one.Vangelis66 commentedon Aug 2, 2026
... As suspected 😜 ; below, code from the
win-153branch:1b4619f#diff-df087f4a19c72b825b28c74758c8ff6d8c30e5b64c6da5dac0d89bc691d85fe7
The original report in #168 mentioned
147.0.4as the minimumr3dfoxversion this LP breakage started to happen on; was that wrong? Is indeed149.0.2the first version this breakage occurs on?Many thanks for your time and efforts into solving this ❤️ ; there was indeed a hint in the code posted in this comment, i.e. problem in the
chrome://browser/content/pageinfo/permissions.jsfile when localised via the official Mozilla LPs...
Manually editing the LP invalidates its signature but, luckily,
r3dfoxhasextensions.langpacks.signatures.required;falseby default 👍 ; and, of course, the user has to perform this manual modification with each
r3dfoxmajor version update 😞 ...Please DON'T 😉 ; though I have a pretty good command of English myself, I do prefer to have the browser localised into my native language, whenever possible; Mozilla, through many international volunteers, go to a lot of trouble to localise the Firefox browser into a plethora of non-English locales; it's my personal view that it'd be a pity to "break" them for the sake of LibreWolf incorporation into
r3dfox(which I've never asked for myself) ... This doesn't mean I don't value ther3dfoxbrowser and your coding efforts, I simply don't fully agree with the direction development has taken...Regards.
Vangelis66 commentedon Aug 3, 2026
Today, after I launched my portable copy of
r3dfox-153.0, my (modified) Greek langpack auto-updated fromgreek_gr_language_pack-153.0.20260727.124451=>greek_gr_language_pack-153.0.20260803.132010practically undoing my manual "fix" and, again, rendering the
PageInfowindow partially broken; so, I had to modify it anew 😞 ; thus, langpack updates should also be considered when mentioning thePageInfo"fix".; unfortunately, even if you disable auto-updates for your modified langpack, if you manually click the master "Check for updates" option in the add-ons manager (about:addons),then the langpack will be force-updated; Firefox doesn't offer a way to permanently block a single extension from updating (apart from modifyingextensions.update.urlinsideabout:config, but that would apply to ALL extensions) ...EDSln commentedon Aug 3, 2026
You can disable updates for individual extensions by clicking on the extension and selecting "Allow auto-updates" → "Disabled" in the window that opens. The same applies to language packs. Even after manually checking for updates, another option simply appears on the left labeled "Available updates"; the extension will not update until you manually allow the update.
Vangelis66 commentedon Aug 3, 2026
@EDSln
You're right 👍 ; I got carried away by something else that applies just to
Pluginsand, more specifically, toWidevineCDM:https://github.com/tchebb/openwv#firefox
K4sum1 commentedon Aug 6, 2026
The main reason I wouldn't for r3dfox is that I would need to go through with this massive task by hardcoding everything or effectively hardcoding everything but keeping the same file structure and it would be inefficient on the compiler side. I would then need to maintain this across every version.
If I go full into developing https://github.com/Eclipse-Community/eXPlorer and/or https://github.com/Eclipse-Community/eXPlorer-Quantum, I would probably do it for the project since both are in a transition period of localizations with double the bloat. I would expect considerably smaller runtime sizes by hardcoding it all, and faster compile times as well.