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

Chrome not reloading page until mouse hovers over browser window #123

Open
jamilabreu opened this issue Nov 27, 2014 · 12 comments
Open

Chrome not reloading page until mouse hovers over browser window #123

jamilabreu opened this issue Nov 27, 2014 · 12 comments

Comments

@jamilabreu
Copy link

On Yosemite/Chrome using the LiveReload extension, everything works fine - except that the page only reloads styles (css/scss/sass) when the mouse hovers over (literally passes above any part of) the Chrome browser window.

Came across similar thread here: https://groups.google.com/forum/#!topic/mimosajs/A7Kbf6plBd0

Thoughts?

@javiercr
Copy link

Same problem here! :(

@toliklunev
Copy link

+1

2 similar comments
@iAnton
Copy link

iAnton commented Mar 19, 2015

+1

@andyhennie
Copy link

+1

@iAnton
Copy link

iAnton commented Mar 24, 2015

increased additionalWaitingTime value to 50 helped me

additionalWaitingTime = 5;

From this issue - livereload/livereload-extensions#26

@didia
Copy link

didia commented May 11, 2015

I have tried to investigate this issue but I can't reproduce it on my mac Yosemite. Chrome is reloading fine, what's your environment?

@whitneyland
Copy link

Real issue, really breaks your rhythm. OSX 10.10.3.

@whitneyland
Copy link

@iAnton 's fix worked for me. Steps to hack/fix:

  1. Finder, Goto folder..., ~/Library/Application Support/Google/Chrome/Default
  2. In extensions folder, find the one with version 2.1 (or your livereload version)
  3. Modify source as shown in patch above

@jibiel
Copy link
Member

jibiel commented Sep 21, 2015

#136 should fix the problem.

@e2
Copy link
Contributor

e2 commented Oct 17, 2015

I can merge #136, as long as it's confirmed that it helps (please add +1s there if it helped you!).

There should be a better fix than just increasing a timeout - but increasing a timeout is till better than people patching their JS files manually.

For speed, maybe it's better to loop over a smaller timeout - but maybe better debugging could help understand the issue.

@jibiel
Copy link
Member

jibiel commented Oct 17, 2015

Maybe we can have an option with the default value for that. It could be passed to the guard :livereload block.

e2 added a commit that referenced this issue Oct 18, 2015
See issue #123 for more info about the workaround
@e2
Copy link
Contributor

e2 commented Oct 18, 2015

In case it helps, there's no longer a need to edit the file manually: #147

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

No branches or pull requests

9 participants