937377 - [e10s] Selecting an item in a <select> does not trigger onChange

Status: RESOLVED FIXED

(Firefox :: General, defect)

Description

[Tim Abraldes [:TimAbraldes] [:tabraldes]]

STR:
With e10s enabled, go to any open bug in bugzilla.mozilla.org and try to set its status to RESOLVED.

Normally a second <select> would appear for you to select a resolution, but with e10s enabled, the second <select> never appears

Comment 1

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Attachment: select-element-onchange

Changing selectIndex apparently doesn't fire the onchange handler.

Comment 2

[:Felipe Gomes (needinfo for replies!)]

Metro seems to use a different version of initEvent for this same functionality, but I can't find the definition for that function anywhere.. http://mxr.mozilla.org/mozilla-central/source/browser/metro/base/content/contenthandlers/FormHelper.js#699

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

Shouldn't we dispatch change event only if the value actually changes.
So perhaps if (this.element.selectedIndex != message.data.value) ...

Comment 4

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/0af44c4131fb

Comment 5

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/0af44c4131fb