666747 - Updating bug in Google Chrome causes drop down select boxes to change values randomly

Status: RESOLVED DUPLICATE of bug 584742

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Chris Germano]

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30
Build Identifier: 3.6.2

There are two custom fields that seem to lose their setting when a user in Google Chrome submits changes to a bug. This only happens sometimes which makes me think it's some kind of weird race condition. The drop downs either are reset to blank or take a value one higher in the list. Bugzilla is working fine for our IE and Firefox users otherwise.

Reproducible: Sometimes

Steps to Reproduce:
1. Goto existing bug page that has multiple custom drop down (selects) in Chrome
2. Save the bug without changing these custom field drop downs

Actual Results:  
notice that sometimes the bug is saved with reset drop downs (empty or adjusted to values one higher or so).

Expected Results:  
It doesn't change values of drop downs that users haven't changed

Comment 1

[Frédéric Buclin]

You mention 3.6.2, which is restricted to security fixes only. Did you try to reproduce with 3.6.5 or 4.0.1?

Comment 2

[Chris Germano]

We just deployed bugzilla for the first time a few months back and it's maintained by our IT so I'm not sure if we can simply change versions. If upgrades are usually simple I can request it. Otherwise if there's more info I can provide from client side (post params or such when it does fail), and/or testing on another environment that you could point me to let me know.

Comment 3

[:glob ✱]

this sounds like bug 584742.

Comment 4

[Chris Germano]

Byron, I can definitely reproduce that bug 584742 by going back in Chrome after submitting changes to a bug. The same fields I have a problem with above is defaulting back to the start state which makes me believe these are related. However like I mention I'm having the same problem when I save but it's not always happening as much as actually going back in the browser so this problem could be reproducible both in saving and going back.

Comment 5

[Max Kanat-Alexander]

Okay, yes, these are the same problem.