When going back to a page on Drupal.org, the scroll position is not remembered on that page. Really annoying when going from a long dicussion, then to a new page, and then Back to the discussion, yo are always taken to the top of the page. This only happens when using Firefox (1.0.3) on Windows.

I have a feeling that this could be a cahing issue. Going Back and Forward with IE is much faster, but Firefix seem to reload every page (unnecessary server load?)

Firefix/Win is tested with the same result on two computers.

Comments

Andrzej7’s picture

Andrzej7 commented

I have the same problem

Andrzej

junyor’s picture

junyor commented

This sounds more like a Firefox bug than a Drupal bug. There are already several reports in Bugzilla:

https://bugzilla.mozilla.org/show_bug.cgi?id=210992
https://bugzilla.mozilla.org/show_bug.cgi?id=258133
https://bugzilla.mozilla.org/show_bug.cgi?id=283524
https://bugzilla.mozilla.org/show_bug.cgi?id=215405

anders.fajerson’s picture

anders.fajerson commented

Well, seems to be fixed now...

anders.fajerson’s picture

anders.fajerson commented

I was wrong, it's not fixed.

And how about the fact that pages aren't cached (try for example to toggle between http://drupal.org/ and http://drupal.org/cvs with Firefox/Win?

Is that intentional?

junyor’s picture

junyor commented

They aren't cached because Firefox doesn't cache pages without Cache-Control headers, IINM.

anders.fajerson’s picture

anders.fajerson commented
Title: Scroll position not remembered on Firefox/Win » Usability drawbacks when not cahing pages on Drupal.org
Status: Closed (won't fix) » Active

I'm opening this again with a new title (instead of opening a dublicate issue).

They aren't cached because Firefox doesn't cache pages without Cache-Control headers, IINM.

Is this necessary?

I suspect this to cause the following usability drawbacks on Drupal.org (at least on Firefox/Win):
1. Scroll position is not rememberd when going back to a page
2. The new fast browser navigation in Firefox 1.5 Beta doesn't work
3. Filled in form fields get erased when (accidently) navigating away from the page

Also, doesn't this cause unnessecary server load?

junyor’s picture

junyor commented

As I said previously, the problems you're seeing seem to be in Firefox, not Drupal.

anders.fajerson’s picture

anders.fajerson commented

1. I don't see it as a bug with Firefox. If Drupal sais it should reload the page everytime, then it does.
2. I can't think of any other website that behaves this way
3. If the gain is greater by sending the cache header then not sending them, why not do it, even if it's a bug with Firefox?

Actully don't know that much about this cache thing, I'm just seeing it from a user perspective. But if someone can tell me why Drupa.org can't send those cache header, I'd be happy to close this issue.

junyor’s picture

junyor commented

Drupal doesn't say to reload the page everytime. Drupal doesn't say anything. Thus, the browser uses its default behavior. Many CMSes behave the same way, IINM.

anders.fajerson’s picture

anders.fajerson commented

I was of the impression that this was a server setting, not software (drupal). I don't see the same behaviour on the sites I'm using drupal on.

Bèr Kessels’s picture

Bèr Kessels commented

This is a problem with FF, not with Drupal. Konqueror has different(bettter) behaviour with cache etc. It has no problems with Drupal cache reloading at all. Fast back and fwd has been in konq quite long and work very well.

I suggest you also open an issue on firefox' bug system.

anders.fajerson’s picture

anders.fajerson commented

I'm not saying it's a poblem with Drupal, I'm saying it's a problem with Drupal.org.

Mayby someone with knowledge of the server setup (Dries, OSL-folks) could step-up and close this issue of it's not fixable. As I said before, if the cache-headers can't be sent (if thats the "problem"), I'd be happy to close this issue.

This was not intended to be a debate about different browser, but a suggestion to improve the experience for Firefox users.

anders.fajerson’s picture

anders.fajerson commented
Category: bug » feature

...thus changing the status to feature request.

killes@www.drop.org’s picture

killes@www.drop.org commented
Status: Active » Closed (won't fix)

it is a browser problem

moshe weitzman’s picture

moshe weitzman commented
Component: web site » Other
Status: Closed (won't fix) » Closed (duplicate)

http://drupal.org/node/109941