flesler / jquery.localScroll

Animated anchor navigation made easy with jQuery

Home Page:http://demos.flesler.com/jquery/localScroll/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not working only in Windows Chrome (OSX Chrome and all other Windows browsers work fine).

wvandaal opened this issue · comments

Just discovered this anomaly where the plugin seems to be totally unresponsive on Windows Chrome 33. I've read through the other closed issues and some similar Stack Overflow questions but to little avail. I'd be interested to know if anyone else has had this problem and what their solution was. You can see the website in question here: http://wvandaal.github.io/

Your site works fine for me on Windows Chrome 33.0.1750.117

On Sat, Mar 1, 2014 at 6:49 PM, Willem van Daalen
notifications@github.comwrote:

Just discovered this anomaly where the plugin seems to be totally
unresponsive on Windows Chrome 33. I've read through the other closed
issues and some similar Stack Overflow questions but to little avail. I'd
be interested to know if anyone else has had this problem and what their
solution was. You can see the website in question here:
http://wvandaal.github.io/


Reply to this email directly or view it on GitHubhttps://github.com//issues/21
.

Ariel Flesler

Hmm, well this is odd, I can't determine what the difference between our two environments is (same exact version of Chrome etc.). However further experimentation has shown that the problem seems to reside with $.scrollTo, rather than with $.localScroll: I have tried several different manual calls to this function from the console without any effect. In each instance, an array containing the window object is returned as expected but no scrolling occurs. I will continue to test this to see if I can determine the root of the problem.

Maybe you have a Chrome add-on that is causing issues?

On Sun, Mar 2, 2014 at 2:28 AM, Willem van Daalen
notifications@github.comwrote:

Hmm, well this is odd, I can't determine what the difference between our
two environments is (same exact version of Chrome etc.). However further
experimentation has shown that the problem seems to reside with $.scrollTo,
rather than with $.localScroll: I have tried several different manual calls
to this function from the console without any effect. In each instance, an
array containing the window object is returned as expected but no scrolling
occurs. I will continue to test this to see if I can determine the root of
the problem.


Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-36446671
.

Ariel Flesler

Ok so I've continued to mess around with different configurations of my browser and the plugin and continue to be stumped. After disabling all of my plugins, add-ons, etc., I decided to check out your demo site http://demos.flesler.com/jquery/scrollTo/ to see if the problem was localized to my site. Here's the interesting part: your demo works fine, but calling the plugin manually from the console (e.g. $.scrollTo('50%',500); $(window).scrollTo('500px',500); $(window).stop().scrollTo('500px',500); ) yielded no result. Any thoughts?

Also interesting, I started throwing some 'onAfter' callbacks into the $.localScroll call in the console of my own website (e.g. $.localScroll({onAfter: function(){ console.log('bye'); }}); ), and the callback is successfully executed even though the scrolling never takes place.

Tried both examples on scrollTo's demo page on Chrome Windows and it works,
must be something with your console, an add-on or something like that.

On Sun, Mar 2, 2014 at 8:13 PM, Willem van Daalen
notifications@github.comwrote:

Also interesting, I started throwing some 'onAfter' callbacks into the
$.localScroll call in the console of my own website (e.g.
$.localScroll({onAfter: function(){ console.log('bye'); }}); ), and the
callback is successfully executed even though the scrolling never takes
place.


Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-36471278
.

Ariel Flesler

Fixed. Turns out I've been messing around with the new Web Components spec in Chrome and had some of the experimental features flags enabled in chrome://flags. Resetting them to their default values got rid of the problem. Thanks for the help flesler