new proton domain available not listed in preferred protomail domain

[laopewastaken]

proton enabled their new domain proton.me.
( https://mail.proton.me/u/0/inbox )

but is not available in the preferred protomail domain option yet.

[62On61dr90]

Would it be possible to make the list editable?

[vaindil]

I created a new signed version for Firefox that updates the domain list to include mail.proton.me (fork here). Download it from the link below, unzip it, and drag the .xpi file onto your Add-ons page in Firefox to install it. I built a Chromium version as well but I didn't test it.

• Firefox
• Chromium

[tholeb]

I created a new signed version for Firefox that updates the domain list to include mail.proton.me (fork here). Download it from the link below, unzip it, and drag the .xpi file onto your Add-ons page in Firefox to install it. I built a Chromium version as well but I didn't test it.

• Firefox
• Chromium

Hi, for chrome, the manifest is outdated. Need to have version 3, and only 1=one background.service_worker (instead of background.scripts).

Btw, how have you built the extension ? Last time I tried I had a lot of npm errors

[VirtualHorror]

@vaindil I seem to be getting a warning on MS Edge v110.0.1

Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.

I'm able to use the extension but that message seems to be just a warning

Additionally why don't you publish the extension on Chrome web store or MS Edge Web Store?
It would be very useful for a lot of users.
Currently MS Edge displays a notification every time the application is opened mentioning that the extension is in developer mode and it hasn't been closed. There is no way to dismiss the notification permanently - you can either close the dialogue box, or set it to remind you the next time you open the application or in the next 2 weeks...

[vaindil]

@VirtualHorror That warning is related to the Manifest V2 -> V3 transition. I've followed the news about that but not much about the actual developer aspects of it since I only tinker with extensions in my free time, so I'm not sure how much work it would be to transition this to V3.

I spent a few hours trying to get this extension running locally about a month ago, but I was unable to do so. React doesn't have any way of creating a debug build without using a server, and I couldn't debug through a prod build because each build takes forever and it's just much more difficult to do.

I'm sure there's some easy step I missed, but I couldn't figure out how this extension was even developed in the first place, so I gave up.

I'd be happy to maintain the project at least for now if I could figure that out, but I don't want to put it on any stores without actually understanding how to run it locally.

[VirtualHorror]

@vaindil

That warning is related to the Manifest V2 -> V3 transition. I've followed the news about that but not much about the actual developer aspects of it since I only tinker with extensions in my free time, so I'm not sure how much work it would be to transition this to V3.

I see

I spent a few hours trying to get this extension running locally about a month ago, but I was unable to do so. React doesn't have any way of creating a debug build without using a server, and I couldn't debug through a prod build because each build takes forever and it's just much more difficult to do.

You mention React doesn't have any way of creating a debug built without using a server and the builds take a lot of time, would accessibility to a VPS or something of that sort speed up the process? If yes, what resources (in terms of RAM, CPU cores and storage) would it need? I could probably spin up a droplet on https://digitalocean.com if that helps.

[VirtualHorror]

Additionally the unread count badge doesn't seem to be working (The notification works but unread count doesn't)

Any clue why?

[Scallywer]

So I've actually tried to start the transition to v3 on my fork in devel branch but without fully understanding what and how stuff was used in initial development, it's really hard to do this.
Even official instructions are not enough and soo many dependencies are deprecated that its needs a huge refactor.

FYI no store will accept the extension if it's not on v3.

[Scallywer]

I did manage to build it on my development VM but it got corrupted and I have not found time to rebuild it again.

[vaindil]

@Scallywer If you have instructions (or a vague idea) of what I need to do to build it, I'm happy to do as much of the V3 transition work and dependency upgrades as I can. I just couldn't figure out how to properly run it in dev mode since React doesn't allow the creation of standalone dev builds, and an extension has to be a standalone set of files (as far as I can tell).

[Scallywer]

@vaindil It's hard to got though, it's a mountain of compilation warnings and security updates which IMHO need to be done first.
And ofc anytime you update a dependency something can break.
Once all that is resolved, then we'd be familiar with the code enough so that we can make the changes needed for v3 transition.

To answer your question about dev builds, easiest way is to use a Linux VM with vanilla chromium, enable dev mode, and point to the extension in a folder (as we do now, since it's not available in the store).
Then after you make changes, you can build and try.
Chrome as such has a decent debugger for plugins and error messages are sufficient to point in the right direction...
You can also always use breakpoints to debug (since react, as any js framework does not support realtime debugging).

[vaindil]

@Scallywer Sorry, the specific part I couldn't figure out was actually building React for dev mode, since that doesn't seem to be an option. I had to create a full prod build every time, which made debugging virtually impossible (and the builds took like 45 seconds each). If there's no better way, then frankly I'm not interested in maintaining it, because that'd be hell to try to work on. If there's somehow a way to point the browser the React dev server that npm start spins up, then I could work with that, but it doesn't seem possible.