Last Comment Bug 762420 - Reloading a form with dynamically-populated (dependent) <select> drop downs restores the first one and keeps the rest in a broken state
: Reloading a form with dynamically-populated (dependent) <select> drop downs r...
Product: Core
Classification: Components
Component: Layout: Form Controls (show other bugs)
: Trunk
: All All
-- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Jet Villegas (:jet)
Depends on:
  Show dependency treegraph
Reported: 2012-06-07 03:22 PDT by kamranali5
Modified: 2014-10-26 15:12 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description User image kamranali5 2012-06-07 03:22:46 PDT
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.52 Safari/536.5

Steps to reproduce:

This problem only exists in firebox. go to that page un the search on left. First select Make, then model, then next field. Then press f5 on keyboard.

Actual results:

After you press f5 you will notice it will only refresh first postback on page which will be make and if you look under model as it hasnt repopulated search althou make is selected there is no models in model field.  You will have to select another makefrom list then re-select the make you want to refresh models.

Expected results:

This works fine in crome if you press refresh just will got back to start intail start values. It doesnt matter which field you post, the very first postback you do is remembered. the version of firebox is 11.0
Comment 1 User image Stefan Weiss [:sir_none] 2014-09-03 14:11:33 PDT

I can confirm that the first dropdown is not set back at a refresh.
in the backend it is unselected, but you can see the last setting.

on Chrome and IE11 it is OK - so i think it is not the page.
Comment 2 User image Nickolay_Ponomarev 2014-10-26 15:12:32 PDT
Can't find an exact duplicate, but it's expected behavior: we try restore to restore forms on reload, but we can't always succeed when the form is dynamically modified by the JS.

Note You need to log in before you can comment on or make changes to this bug.