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

Latest version in Firefox #510

Open
mugnap opened this issue Dec 14, 2020 · 8 comments
Open

Latest version in Firefox #510

mugnap opened this issue Dec 14, 2020 · 8 comments

Comments

@mugnap
Copy link

mugnap commented Dec 14, 2020

Hello, I upgraded to the latest version to solve the issue under Firefox (infinite loading). The issue seems to be still there: pace loads for a lot of time, while under Chrome I have no issues. I noticed (at least in Firefox) that if I move the mouse while pace is loading, it correctly finishes. How these things may be related?
Thanks!

@mwi812
Copy link

mwi812 commented Jan 6, 2021

I´ve exact same issue. I already implemened this code from stackoverflow, so the loading bar finish 100%, also if i don´t move the mouse but the loading time are horrible in FF. Chrome and Edge are perfect ....

Loading Time Chrome and Edge <1s
Loading Time FF > 15 Seconds

https://stackoverflow.com/questions/43887415/pace-js-never-reaches-100/51343315#51343315

Temp. workaround is #470 (comment)

@S4nG0
Copy link

S4nG0 commented Jan 13, 2021

Is there no intention of fixing this bug? Is it even fixable?

I tried every workaround, but loading still takes up to 20secs on Firefox, which makes using pace not even worth it to be honest...

@thehydrogen
Copy link

I'm also having this problem, is there any solution that someone might have found?

@PierreAronnax
Copy link
Contributor

PierreAronnax commented Feb 17, 2021

This is caused specifically by the Event Lag feature.
I have disabled it myself.

paceOptions = {
  eventLag: false, // disabled
};

Or you can increase the threshold (30 is just a random guess):

paceOptions = {
	eventLag: {
		lagThreshold: 30,
	},
};

The default lagThreshold is 3 and should be increased.

@bsantosdev
Copy link

@PierreAronnax thank you for the input. The first workaround worked like a charm for me.

@Igor82620
Copy link

thanks for your effort. You are my time saver.

@lipflip
Copy link

lipflip commented Jan 26, 2022

This is caused specifically by the Event Lag feature. I have disabled it myself.

paceOptions = {
  eventLag: false, // disabled
};

Or you can increase the threshold (30 is just a random guess):

paceOptions = {
	eventLag: {
		lagThreshold: 30,
	},
};

The default lagThreshold is 3 and should be increased.

Thanks, is working!

@joseadrian
Copy link

This is caused specifically by the Event Lag feature. I have disabled it myself.

paceOptions = {
  eventLag: false, // disabled
};

Or you can increase the threshold (30 is just a random guess):

paceOptions = {
	eventLag: {
		lagThreshold: 30,
	},
};

The default lagThreshold is 3 and should be increased.

That worked!! 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

9 participants