ykuramochi / jquery-jsonp

Automatically exported from code.google.com/p/jquery-jsonp
0 stars 0 forks source link

Page flickering #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
Any page request via the API

What is the expected output? What do you see instead?
I see page refreshing.

What version of the product are you using? On what operating system?
1.1.0

Please provide any additional information below.
It appears that using this API--as far as I can tell--causes 
page "flicker" in that the page appears to be refreshed whenever an AJAX 
call is made via the API. When I say "refreshed", I mean simply that you 
see the window title "flicker" to something else and back again, at least 
in Firefox tabs. If I switch back to the regular jQuery's JSONP API, this 
issue goes away.

Original issue reported on code.google.com by skn...@gmail.com on 15 Oct 2009 at 10:00

GoogleCodeExporter commented 8 years ago
Yep, it's an issues I forgot to add in the KnownIssues section. This is due to 
the 
fact jQuery.jsonp uses iframes internally.

I use the plugin in several production environments and this has never been a 
big 
deal. However, I'll keep this open because, despite all my searches, I never 
found a 
way to prevent this behaviour.

So, if anybody has a cross-browser way to prevent the browser's animations from 
firing when an iframe is loading, I'll gladly take it :)

Original comment by aubourg.julian on 16 Oct 2009 at 7:47

GoogleCodeExporter commented 8 years ago
We've gone to using your API for user-instigated AJAX calls but falling back on 
regular jQuery JSONP when we're doing asynchronous data updates (not user-
instigated). This works pretty well and is a decent compromise.

Original comment by skn...@gmail.com on 16 Oct 2009 at 11:15

GoogleCodeExporter commented 8 years ago
I looked as much as I could into this. There is no way on earth browsers will 
stop
"shouting" whenever a iframe is loading :(

Will not be fixed I'm afraid, unless someone on the web finds a workaround in 
the future.

Original comment by aubourg.julian on 5 Nov 2009 at 1:34

GoogleCodeExporter commented 8 years ago
jQuery uses destructive methods to obtain values e.g. reading dimensions in the 
most
unexpected ways. These methods may cause the browser to refresh the page.

An example: http://dev.jquery.com/ticket/5743

http://groups.google.com/group/jquery-en/browse_thread/thread/567ec8c073648a8a

While the above cases might not directly apply to this issue, it might pay to 
get to
the bottom of it deep inside of jQuery and ask the authors of jQuery to remove 
such code.

Original comment by bht...@gmail.com on 19 Jan 2010 at 5:02

GoogleCodeExporter commented 8 years ago
The problem regarding jQuery you're mentionning is completely unrelated to the 
issue
at hand. What we're talking about here is browsers chrome activity (ie: loading
animation into tabs or titlebars)

Original comment by aubourg.julian on 21 Jan 2010 at 3:47

GoogleCodeExporter commented 8 years ago
Forgot to mention this should be fixed as of 2.x.

Original comment by aubourg.julian on 27 May 2010 at 10:47

GoogleCodeExporter commented 8 years ago
Issue 17 has been merged into this issue.

Original comment by aubourg.julian on 27 May 2010 at 10:48