Skip to content
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

Closed
KieranCodema opened this issue Jul 17, 2024 · 5 comments
Closed

[BUG] Extension pushes events around #31

KieranCodema opened this issue Jul 17, 2024 · 5 comments

Comments

@KieranCodema
Copy link

KieranCodema commented Jul 17, 2024

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

  1. The extension just needs to be turned on for the bug to be seen. The calendar needs to be populated with events.

  2. Screenshot of how it looks with extension disabled image

  3. Screenshot of how it looks with extension enabled CalMerge_Kieran_ExtensionOn

Expected behaviour

  1. Expect calendar items to stay where they are.

Device

  • OS: Windows 11
  • Browser: Chrome Version 126.0.6478.127 (Official Build) (64-bit)
  • Extension Version: 2.3.7

Additional context
List of Errors:
image

Uncaught (in promise) TypeError: fillOptions[fill_style] is not a function:
image

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'style')
image

Uncaught (in promise) Error: Extension context invalidated.
image

@macintacos
Copy link

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.

@manuellazzari-cargoone
Copy link

@macintacos same, I reported the same below, closing mine since this is much better reported

@HCAWN
Copy link
Owner

HCAWN commented Jul 20, 2024

Hi @manuellazzari-cargoone @KieranCodema @macintacos ,

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

@manuellazzari-cargoone
Copy link

manuellazzari-cargoone commented Jul 21, 2024 via email

@KieranCodema
Copy link
Author

KieranCodema commented Jul 22, 2024

Hi @HCAWN
Now that I'm on version 2.38, it's working perfectly. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants