select tag doesn't update it's status on refresh




4 years ago
4 years ago


(Reporter: bert.bruynooghe, Unassigned)


33 Branch
Mac OS X

Firefox Tracking Flags

(Not tracked)




4 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141030112145

Steps to reproduce:

simple html being served:
 <option selected>2</option>

Open the html in browser=> 2 is selected
change option to 1 in browser
refresh (not shift refresh)

Actual results:

get 304 (expected) and status of input is still option 1 (unexpected)

Expected results:

should have option 2 again, as that is what in the served html.

Comment 1

4 years ago
I'm not able to reproduce it with FF34 on Win 7, I got the option "2" after refreshing the page.

Could you force the update to FF34 in the options and test again.
If that fails, could you test with a clean profile (
Flags: needinfo?(bert.bruynooghe)

Comment 2

4 years ago
Sorry, it is not possible for me right now to update to FF34, as I currently need to write a workaround for these problems, and I need some means of testing those. Same problem occurs on other user's machines, so I doubt that creating a clean profile would solve the issue on FF33.
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
I see the behavior described (on Linux).  But I thought it was generally considered a feature that we preserve form state across reloads.  (Though I admit I generally don't want that behavior.)
Component: Layout: Form Controls → Document Navigation
Flags: needinfo?(bert.bruynooghe)

Comment 4

4 years ago
Still seeing the same behaviour on FF34 on OSX. 
I agree that would maybe be a good feature to preserve state across reloads, but then it must be taken further. The issue I had was that there were input fields hidden/unnamed based on the value of the select (done by javascript), but that state was definitely reset. I had to add some code to have the page initialize the inputs upon reload, which then again caused FUOC.
You need to log in before you can comment on or make changes to this bug.