Hey, I'm the creator of the blogging platform he's running on and am trying to replicate this. Do you have cookies or js off or any other notable change from stock?
I do use a few addons (Flashblock, Adblock plus, Ghostery) that possibly could cause side effects, but since Chrome also causes problems for some I doubt that it's a Firefox specific bug.
I believe this issue is fixed now... feel free to give it a try and let me know if you're still having issues.
Thanks to everyone for the detailed info-- really helped me a lot.
For those interested, here's what happened:
When someone goes to a SETT blog, the first thing we do is fire off an ajax call to see if we can set a 3rd party cookie. If we can't, we bounce to a page on sett.com that sets a cookie and then redirects back. In some cases, like Safari with default settings, this allows us to use a 3rd party cookie.
To prevent infinite looping in cases where 3rd party cookies can't be accessed, we add a query string to the URL, telling SETT to skip the cookie check.
However, the old way we were doing it was just appending ?_ to the URL, rather than parsing it out and taking into consideration the query string of the URL.
This URL was submitted with a trailing ?, which made the query string ??_, which didn't properly skip the cookie check. Thus... infinite refreshes.
I got a weird and similar problem. The page looked like it was just continually reloading parts (most) of itself, 2 to 3 times per second. I stopped if I clicked the stop button and all was well. Chrome for mac, normal config except 3rd party cookies blocked. Google Page Insights and YSlow enabled.
Hey, I created the blogging platform he's running on. Would you mind giving me some details on the scrolling problem you're having? Do arrows, mouse wheel, and scroll bar all not work?
Firefox 19.0 and XP here with cookies and javascript enabled. I can scroll down but it jumps back up to the top and nothing I can think of (holding the scroll bar fixed, etc.) keeps it from bouncing up.
@baking description was more accurate. While scrolling, the browser jumped back up. But it works now, so it must have been caused by a bug in their redirect loop that is described in this thread, not by the blogging platform bug.
