LinkHints breaks Proton mail

[akiross]

Steps to reproduce

1. Go to mail.proton.me
2. Log in, open your inbox
3. Enable column layout
4. Switching to a different mail will break the preview
5. Trying again with LinkHints disabled yields different results

Screen shot

Description

When LinkHints is enabled, Proton Mail will fail and break with a message "Something went wrong. Please refresh the page or try again later.". When the page is reloaded, the selected mail (if any) will load properly, but upon switching email, the error will pop up.

The Developer console shows this kind of messages (related to proton's webpack build):

TypeError: can't access dead object
    useLinkHandler.tsx:158
    ...

which do not appear when LinkHints is disabled.

Debug info

Debug info

{
  "version": "1.3.3",
  "browser": "firefox",
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0",
  "browserInfo": {
    "name": "Firefox",
    "vendor": "Mozilla",
    "version": "130.0.1",
    "buildID": "20240913135723"
  },
  "platformInfo": {
    "os": "linux",
    "arch": "x86-64"
  },
  "storage.sync": {
    "autoActivate": false
  },
  "storage.local": {
    "tutorialShown": true
  },
  "language": "en-US"
}

[ludams]

I have the same issue, which is really annoying. Fixing the problem properly would obviously be the best solution for everyone. But in the meantime I created a workaround for myself by disabling the extension for the ProtonMail website by modifying the src/manifest.ts file.

I added for both content_scripts the property exclude_matches with a single entry of "*://mail.proton.me/*". The result looks something like this:

export default (): string =>
  toJSON({
    // ...
    content_scripts: [
      {
        matches: ["<all_urls>"],
        exclude_matches: [
            "*://mail.proton.me/*",
        ],
        // ...
      },
      {
        matches: ["<all_urls>"],
        exclude_matches: [
            "*://mail.proton.me/*",
        ],
        // ...
      },
    ],
  });

And then I built and installed the extension by following the description in the Contributing documentation.

I hope this helps someone :)