[BUG] Native messaging extensions fo not work #219

New issue

Closed

opened 2025-12-23 13:46:27 +01:00 by cuche · 1 comment

cuche commented

2025-12-23 13:46:27 +01: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?

Arch Linux

Other

No response

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

146.0.1 (Phoenix: 2025.11.27.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?

default

No response

keepassxc-browser@keepassxc.org
plasma-browser-integration@kde.org

Please explain the issue you are experiencing.

Extensions requiring native messaging (I'm using Plasma and KeepassXC integrations) does not work at all. After some investigating, I noticed that in about:config there are two additional values not present in vanilla firefox:

webextensions.native-messaging.max-input-message-bytes
webextensions.native-messaging.max-output-message-bytes

both are set to 0 and those prevent all native messaging based extensions to work. Setting the values to 1048576 restores the original Firefox behavior.

This change is not documented on the wiki and should be added to the Website compatibility page in the Extensions section since it breaks KeepassXC which is a recommended one. Or as an alternative, just remove those preferences.

Please provide detailed steps to reproduce the issue.

Read above.

### 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? Arch Linux ### Other _No response_ ### What version of Firefox/Gecko and Phoenix are you using? 146.0.1 (Phoenix: 2025.11.27.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. _No response_ ### Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed. * `keepassxc-browser@keepassxc.org` * `plasma-browser-integration@kde.org` ### Please explain the issue you are experiencing. Extensions requiring native messaging (I'm using Plasma and KeepassXC integrations) does not work at all. After some investigating, I noticed that in about:config there are two additional values not present in vanilla firefox: * `webextensions.native-messaging.max-input-message-bytes` * `webextensions.native-messaging.max-output-message-bytes` both are set to 0 and those prevent all native messaging based extensions to work. Setting the values to `1048576` restores the original Firefox behavior. This change is not documented on the wiki and should be added to the Website compatibility page in the Extensions section since it breaks KeepassXC which is a recommended one. Or as an alternative, just remove those preferences. ### Please provide detailed steps to reproduce the issue. Read above.

cuche added the

bug

label

2025-12-23 13:46:27 +01:00

celenity self-assigned this

2025-12-24 02:41:29 +01:00

celenity commented

2025-12-24 02:41:32 +01:00

Owner

Thanks for the report. Native messaging will definitely remain disabled by default, but I just added these extensions to the Web compat wiki page for reference.

Thanks for the report. Native messaging will definitely remain disabled by default, but I just added these extensions to the [Web compat wiki page](https://codeberg.org/celenity/Phoenix/wiki/Web-Compat) for reference.

celenity

2025-12-24 02:41:33 +01:00