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

Timeline not working in Safari 12 #76

Open
jeffwhitfield opened this issue Oct 15, 2018 · 5 comments
Open

Timeline not working in Safari 12 #76

jeffwhitfield opened this issue Oct 15, 2018 · 5 comments

Comments

@jeffwhitfield
Copy link

Just installed this extension for testing. So far, so good. :D However...

Appears the Timeline feature doesn't work in the latest versions of Safari on MacOS Mojave. Works great in Chrome though. In Safari, none of the bars show up...just the rows showing the name of the tasks followed by a grey bar. So...something is askew! :P

@Ethan3600
Copy link
Owner

Hi @jeffwhitfield. Thanks for using the CJM

I'll admit, I did 100% of my development on Firefox.

Thanks for logging this bug!

@jeffwhitfield
Copy link
Author

jeffwhitfield commented Oct 16, 2018 via email

@schmengler
Copy link
Contributor

FWIW, on Chrome the graph did not load until I scroll down and then wait a few seconds

@Ethan3600
Copy link
Owner

Ethan3600 commented Feb 16, 2019

@schmengler ya it's a bug as a result of a fix for issue #50

Basically, we're removing elements (the cron "marks") from the DOM if a cron job's "mark" isn't within the view port (screen/timeline component) and adding them back if the condition is reversed. We're doing this for performance reasons. The check (to see if the "mark" is within the view port) gets triggered when you scroll around.

There's probably a cleaner solution for this, but I've been struggling with the aforementioned issue for a while. Luckily, it's not a show stopper 🙏 and we did get a major performance boost when we push closer to 10k, even 20k crons on the timeline (which in theory shouldn't happen, but 🤷‍♂️ )

@fredden
Copy link
Collaborator

fredden commented Oct 17, 2023

@jeffwhitfield I don't have access to Safari right now to test this. I wonder if the changes applied in #200 may have fixed this. Would you be able to test again with version 2.1.4 and report back?

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