Closed
Bug 1136356
Opened 10 years ago
Closed 9 years ago
Protonmail shows "No connection" error in Nightly.
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: swilkes, Unassigned)
Details
Attachments
(1 file)
261.63 KB,
image/png
|
Details |
I use Protonmail (encrypted email hosted in Switzerland). For about a week, Nightly has been telling me Protonmail has no Internet connection only when I try to send a message, but I do have a connection: Protonmail is saving drafts and I can access anything else online via nightly. See screenshot.
I am not selecting "encrypt for outside users" in this case, though that doesn't appear to make a difference.
I have the Nightly dev tools open so let me know what, of that, I can attach to this bug that might be helpful.
Reporter | ||
Comment 1•10 years ago
|
||
Any update on this? This continues to happen in Nightly.
Component: General → Session Restore
Updated•10 years ago
|
Component: Session Restore → General
Comment 2•10 years ago
|
||
I confirm this bug of ProtonMail when I am using Firefox Developper Edition. I tried with IE and my message was sent.
Comment 3•9 years ago
|
||
Lumping into untriaged so it gets triaged - as it is, it's not clear what's causing that alert and if there's a Firefox bug that's being triggered, or if this should be in tech evangelism and we need to talk to the protonmail people to get it fixed - or maybe, given how old this bug is, they already fixed it...
Component: General → Untriaged
Comment 4•9 years ago
|
||
Hi,
I tested this issue on the latest Nightly (48.0a1, Build ID 20160327030437) and I can't reproduce the issue. I can send mails, receive a "Message Sent" confirmation, and can confirm that the person I sent the mail to actually received it.
Considering the fact that the reporter has disabled his/her account and the fact that I can't reproduce the issue, I am marking this as Resolved-WORKSFORME.
Thanks,
Cipri
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•