搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

At espn score 50-40 on auto refresh page, navigate to dif page at espn hit back button score is now 15-12 when score actually increased to 60-55?

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 synche

more options

I navigate to espn.go.com. Go to the NBA page, where they have scores of games going on that they refresh, so you get a pretty current score that is regularly updated. Say the score for the Kings game is 50-40. I click on standings to see the NBA standings. When I click the back button, I get to a earlier version of the NBA page where the score is 15-12, possibly the first version that loaded. I can understand how the back button might better take you back to where the score was 50-40, than the updated 60-55 page (see original question if this doesn't make sense), although I personally would prefer the most updated page, but why reload an old, from when you navigated away, page? Sorry if the explanation wasn't worded the greatest, but I think you get the gist.

I navigate to espn.go.com. Go to the NBA page, where they have scores of games going on that they refresh, so you get a pretty current score that is regularly updated. Say the score for the Kings game is 50-40. I click on standings to see the NBA standings. When I click the back button, I get to a earlier version of the NBA page where the score is 15-12, possibly the first version that loaded. I can understand how the back button might better take you back to where the score was 50-40, than the updated 60-55 page (see original question if this doesn't make sense), although I personally would prefer the most updated page, but why reload an old, from when you navigated away, page? Sorry if the explanation wasn't worded the greatest, but I think you get the gist.

所有回覆 (2)

more options

Refresh rate is determined by the actual site itself or variables such as your connection & unless you know how or manually tampered with your refresh browser rate has nothing to do with the actual browser itself, rather something on the OS side slowing it down.

more options

I'm sorry if I don't understand your response. Maybe you didn't understand my original question. I think I may be able to express my question better, or maybe I'm just dense, but let me give it another try.

I go to a webpage, it updates itself. I navigate to another page on the website. I hit the back button. This doesn't take me back to the page I was on when I navigated away, but to a previous version, that has already been updated.

I just don't see how this way that mozilla handles a back button is useful to users. I see it as a flaw in the way mozilla handles hitting the back button, but that may just be me.