Paging in Firefox 3 in Linux | Site Feedback

CannotResolveSymbol
{insert caption here}

Thread and forum paging seems to be broken in Firefox 3 in Linux (2008061712, the final release of 3.0) right now: the browser should be running Javascript the same way as Fx3 in Windows, so this would seem to be a browser detection bug.

wisemx
Live it

-> Firefox 3 in Linux <-

Wow, a double negative. Smiley

CannotResolveSymbol
{insert caption here}

In reply to wisemx

#Jun 24th, 2008 @ 6:12 AM

A double awesome 8)

*ducks*

wisemx
Live it

In reply to CannotResolveSymbol

#Jun 24th, 2008 @ 6:39 AM

CannotResolveSymbol
{insert caption here}

Okay, I just cleared my cache and now I can't page in Windows, either... so there's a bug in the latest version of your paging code that's masked because the JS is cached.

wisemx
Live it

In reply to CannotResolveSymbol

#Jun 24th, 2008 @ 8:17 AM

We need a cartoon of these two battling it out:
javascript vs. __VIEWSTATE

HumanCompiler
Compiling humans...and code

We had a problem yesterday that was affecting paging, but it was fixed a few hours later. I just cleared my cache in FF3 (working from home today) and paging seems to be working fine. Are you still seeing this behavior?

HumanCompiler
Compiling humans...and code

In reply to wisemx

#Jun 24th, 2008 @ 10:16 AM

Yes, that would be a good one. We chose no viewstate. Wink

wisemx
Live it

In reply to HumanCompiler

#Jun 24th, 2008 @ 10:47 AM

U rock bro. Smiley

CannotResolveSymbol
{insert caption here}

In reply to wisemx

#Jun 24th, 2008 @ 11:37 AM

I'm still seeing this problem - looks like it is a browser detection issue (not a caching issue as I thought). My current user agent is "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061712 Fedora/3.0-1.fc9 Firefox/3.0" and paging doesn't work (the refresh button does not appear and the next/previous page buttons don't function). If I change my UA to that of Firefox 2 on Windows (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0) and refresh, paging works and the refresh button appears. Changing the user agent back to the default and refreshing again causes paging to stop working again, so this is not a caching issue.

Duncanma
Just Coding for Fun...

In reply to CannotResolveSymbol

#Jun 29th, 2008 @ 10:32 AM

Thanks for posting your user-agent, I'll see what happens when that hits our browser detection code (I believe we just use the built-in asp.net stuff to get the major/minor version and browser name)

CannotResolveSymbol
{insert caption here}

In reply to Duncanma

#Jun 30th, 2008 @ 12:35 PM

I'm bumping this thread again because I'm seeing this issue in other Mozilla-based browsers:

Firefox 3.1 nightlies: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1a2pre) Gecko/2008073003 Minefield/3.1a2pre
K-Meleon on Windows: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17pre) Gecko/20080716 K-Meleon/1.1.6

Changing the user agent of either browser to that of Firefox 2 will correct the issue and everything works as expected. I'd assume that other browsers, like Camino and Seamonkey, will also see the same error, but I can't test them right now.

Please respect your users' browser choices by detecting Mozilla-based browsers correctly (by looking for Gecko/ in the User Agent string rather than Firefox, and looking at the number following rv: if you need specific features).

HumanCompiler
Compiling humans...and code

In reply to CannotResolveSymbol

#Jul 30th, 2008 @ 5:47 PM

I believe we do look for Gecko, but I'm adding this as a bug to our list to investigate. Thanks!

Rowan
Look, no errors.

In reply to HumanCompiler

#Aug 4th, 2008 @ 10:14 AM

I'm having the same problem, none of the paging works.

Firefox 3.1 Alpha 1

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1a1) Gecko/2008072310 Shiretoko/3.1a1

I have to disable JS completely to be able to change pages.

Sampy
This will be the sixth time we have destroyed it and we have become exceedingly efficient at it

In reply to Rowan

#Aug 11th, 2008 @ 1:36 AM

We'll look into it but there's always a chance that the problem might be the Firefox Alpha and not us.

We've had problems in the past with betas of Firebug and even Imageshack toolbars.

Rowan
Look, no errors.

In reply to Sampy

#Aug 11th, 2008 @ 8:33 AM

CannotResolveSymbol already reported that switching the UA gets around the issue.

HumanCompiler
Compiling humans...and code

In reply to Rowan

#Aug 12th, 2008 @ 1:51 AM

As I mentioned above, we entered this bug into our bug tracking system.

Starting next week, we're going to try out having a bug triage meeting Thursday afternoons and bug bash as a group on Fridays. We'll let you know how it goes.