-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Calendar Button not working #579
Comments
Thanks for the report. I didn't notice this new feature before publishing the 5.1.3 release and so didn't try it in action. |
There is no easy fix as they use iframe for embedding the entire calendar web app on the side panel vs mounting calendar-related components into the same page/DOM. |
Thanks for the analyze. Maybe in future Releases will it work 👍 👍 👍 |
Any news on this issue? |
I tried some ideas in |
Is this the same reason why Proton Drive doesn't work? |
It's not. Drive supposed to work, for long time. Try relogin if it doesn't. |
Drive stopped working for me since version v5.1.7 i believe. I hoped it would work after an update which i just did, but still no luck. edit: seems to be solved now somehow. |
The bug occur again with same error message in the log. |
It was not fixed, so of course it occurs again. I mean the calendar button issue. |
Did you drop that bug or will you fix it ? |
This issue remains open, so there is a chance for it to get fixed one day. But I'm not ready for another attempt, iframe stuff is a mess to work with. There is still a hope that Proton converts iframe use for calendar embedding to a regular single page application approach, how it's supposed to be these days, so then the issue gets self-resolved. |
To reduce confusion, the next release comes with cut out Calendar icon. Already implemented in the |
With the new(?) Version from Proton Mail Client I see on the right panel a new Button for the Calendar, but it doesn't work with ElectronMail. In the Browser it works fine and open the Calendar.
Following errors in the logfile:
The text was updated successfully, but these errors were encountered: