搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox 4 refresh bug -- option selected change not reflected on refresh

  • 4 个回答
  • 64 人有此问题
  • 12 次查看
  • 最后回复者为 QuestPC

more options

There is a bug in refreshing the display for a form when a change has been made to option selected. I reproduced the problem with the small file below -- this works in other browsers including Firefox 3.x -- if you display the page, update the option selected for example in person 2 change option selected from none to Dennis and refresh the page the browser will not update the display but a look at the page source shows the "updated" information. I reproduced using Firefox 4 on windows XP and windows 7.

There is a bug in refreshing the display for a form when a change has been made to option selected. I reproduced the problem with the small file below -- this works in other browsers including Firefox 3.x -- if you display the page, update the option selected for example in person 2 change option selected from none to Dennis and refresh the page the browser will not update the display but a look at the page source shows the "updated" information. I reproduced using Firefox 4 on windows XP and windows 7.

所有回复 (4)

more options

You have to bypass the cache to clear already entered data in a form.

Reload a web page and bypass the cache with:

  • Press and hold Shift and left-click the Reload button.
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Cmd + Shift + R" (MAC)
more options

Add the HTML attribute autocomplete="off" to any <select> or <input> you do not want to see this behaviour on.

more options

With old versions of Firefox it was possible to fix aggressive client-side caching by restoring of the form values programmatically in Javascript body.onload handler. With FF4 now this does not work. I set selected option values, these are properly stored in DOM tree (according to Firebug inspector), however visual display of select/option is not updated. This is a plain bug, imo.

more options

I mean, doing aggressive-cache way, it should not execute body.onload handler, or it should respect DOM values set by Javascript onload handler. Currently it executes Javascript handler, updates DOM tree and NOT re-rendering it which is plain wrong (DOM and visual representation do not match).