[Bug] Stuck on hyperlink modal

[KaKi87]

Hello,

When writing an email, once the hyperlink modal is opened, I can't close it, whether I validate or cancel.

Thanks

[vladimiry]

Can you verify if this build affected? It's a work-in-progress build assembled as a result of #332 work.

[vladimiry]

• The actual app code doesn't use https://github.com/ProtonMail/WebClient/ project anymore but https://github.com/ProtonMail/proton-mail.
• There is no confirmation that https://github.com/ProtonMail/proton-mail demonstrates the placed issue.
• A new app version with Support @ProtonMail web client apps stack v4.1.0+ #332 change included is going to be released soon. Probably this week.

[KaKi87]

Hello,
Mega.nz is not working for me, could you try a website that supports direct download ?
Thanks

[vladimiry]

website that supports direct download ?

No such option at the moment.

[KaKi87]

anonfile.com, file.io, etc.

[vladimiry]

Package type to upload (linux/macos/win)?

[KaKi87]

AppImage please.

[vladimiry]

https://anonfiles.com/Bav1F9f0p4/electron-mail-2020-10-13-v4.9.0-b3aac8a_tar

[KaKi87]

The bug is fixed in this build, thanks.

[vladimiry]

Just for you to know. In the build I shared the remote requests to the URL origins other than selected in the "API entry point" dropdown value are blocked by default. So for example you won't be able to load inlined in the email message images. In the released version this is going to be an opt-in feature (disabled by default).

[vladimiry]

https://anonfiles.com/Bav1F9f0p4/electron-mail-2020-10-13-v4.9.0-b3aac8a_tar

I don't recommend using this build on daily basis but only testing the original issue case since I have a reason to believe that this version comes with proton web client that has a leading to the privacy-compromising flaw (the issue has been reported). For the same reason, I would not yet use the https://beta.protonmail.com in the browser.

[KaKi87]

I see, could you please link me that issue ?

[vladimiry]

link me that issue ?

The issues of this type are not supposed to be publicly disclosed until they get fixed. I'm going to place update message in #332 when I get new information.

[tianalemesle]

So, I'm back on v4.8.0, and I can no longer reproduce the bug ? Is it possible that it is still using the same website as in v4.9.0 ?

[vladimiry]

Is it possible that it is still using the same website as in v4.9.0 ?

Unlikely since the proton's web client packaged in the app is a static asset. But technically it's possible for proton client to load the JS stuff from a remote server and then embed it to the page (I don't think they do that). In not yet released v4.9.0 the Blocking all non "API entry point"-based network requests feature is enabled in order to detect/block unintended/shady network requests, see #312 (comment) for details. By the way, enabling that option suppresses the issue I mentioned in the previous message.

[vladimiry]

The most recent v4.9.0 build uploaded here. The named before issue gets suppressed by enabling Block non "API entry point"-based network requests option (respective screenshot posted in #312 (comment)) but it also means that you won't be able to load inlined in emails images.