Firefox Scroll Position and session.cache_limiter
Posted: Wed Jul 30, 2008 2:41 pm
Hey gang,
I'm having a problem with one of my php websites. Firefox is not remember the vertical position of the page scroll when I either click the back button to go back to a long page that I was in the middle of, or reload a page that was scrolled at a certain position. The page simply reloads like a complete refresh, where the vertical scroll position is at the very top.
Some research on google led me to find that this is a known problem with Firefox, and how firefox handles scroll position with pages using the "no-store" control for cache-control.
http://kb.mozillazine.org/Scroll_positi ... remembered
This "no-store" option is set in the PHP.ini file under session.cache_limiter. Mine is set to the default of:
session.cache_limiter = nocache
It seems that changing the session.cache_limiter to anything other than 'nocache' (for instance, setting it to 'private'), fixes this issue with firefox. However, I have no clue what all this stuff means, and what any consequence may become of changing this default setting of 'nocache'.
So I thought I would ask to get any guidance or suggestions on what I should do here. Has anyone ever fixed this problem on one of your own sites? Any help would be greatly appreciated. Thanks again.
I'm having a problem with one of my php websites. Firefox is not remember the vertical position of the page scroll when I either click the back button to go back to a long page that I was in the middle of, or reload a page that was scrolled at a certain position. The page simply reloads like a complete refresh, where the vertical scroll position is at the very top.
Some research on google led me to find that this is a known problem with Firefox, and how firefox handles scroll position with pages using the "no-store" control for cache-control.
http://kb.mozillazine.org/Scroll_positi ... remembered
This "no-store" option is set in the PHP.ini file under session.cache_limiter. Mine is set to the default of:
session.cache_limiter = nocache
It seems that changing the session.cache_limiter to anything other than 'nocache' (for instance, setting it to 'private'), fixes this issue with firefox. However, I have no clue what all this stuff means, and what any consequence may become of changing this default setting of 'nocache'.
So I thought I would ask to get any guidance or suggestions on what I should do here. Has anyone ever fixed this problem on one of your own sites? Any help would be greatly appreciated. Thanks again.