-
Notifications
You must be signed in to change notification settings - Fork 6
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
[BUG] Extension pushes events around #31
Comments
Was about to report this same thing - I thought I was going nuts until I remembered that I had this installed, disabled it, and all of my events were aligned correctly again. |
@macintacos same, I reported the same below, closing mine since this is much better reported |
Hi @manuellazzari-cargoone @KieranCodema @macintacos , this was an oversight in 2.3.7 Please confirm if you are on this version that the events are where they should be? H |
Works for me, thanks! Awesome extension!
Il Sab 20 Lug 2024, 21:22 Henry Neilson ***@***.***> ha
scritto:
… Hi all,
this was an oversight in 2.3.7
I spotted it and deployed a new build but Google isn't instant so took a
day for 2.3.8
Please confirm if you are on this version that the events are where they
should be?
H
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZC2AIUW2TJAW2U4KJWXBOTZNK2IBAVCNFSM6AAAAABLA4ZYUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGI3DONJTG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi @HCAWN |
Edit: Formatted better and added the errors as additional context
Describe the bug
Events are "moved" when the extension is on. The more calendars active, the more "movement" is seen in events. Events move regardless of if they are merging.
To Reproduce
The extension just needs to be turned on for the bug to be seen. The calendar needs to be populated with events.
Screenshot of how it looks with extension disabled
Screenshot of how it looks with extension enabled
Expected behaviour
Device
Additional context
List of Errors:
Uncaught (in promise) TypeError: fillOptions[fill_style] is not a function:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'style')
Uncaught (in promise) Error: Extension context invalidated.
The text was updated successfully, but these errors were encountered: