Robert O'Callahan 192b5d6603 Bug 821307. Ensure nsTextEditorState::SetValue does nothing when the new value equals the old value, even for password inputs. r=ehsan ... If nsTextEditorState::SetValue is allowed to rebuild the editor DOM even when the new value is the same as the old value, then during PrepareEditor we can remove the content that's the current target of the event triggering the PrepareEditor, which prevents important code from running such as the code that focuses the text input. Normally this isn't a problem but nsTextEditorState::SetValue's code for getting the current value is broken for password controls when !mEditorInitialized. So we remove that broken code path. We have to make sure that the password text, if any, is set on the edit-rules during their initialization so the regular path for getting the current value returns the right thing. --HG-- extra : rebase_source : 81a01a957b4b1e0cf868505a1b23c9110a2f4b3a		2014-04-15 00:33:47 +12:00
..
public	Bug 939044 - Rename remaining MODULE definitions to XPIDL_MODULE. r=mshal	2013-11-19 11:47:43 +09:00
src	Bug 821307. Ensure nsTextEditorState::SetValue does nothing when the new value equals the old value, even for password inputs. r=ehsan	2014-04-15 00:33:47 +12:00
test	Bug 984497 - Use SpecialPowers more and change SpecialPower usage to deal with Window on WebIDL bindings. r=bz.	2014-02-15 22:12:34 +01:00
moz.build	Bug 855465 - Add emacs python mode comments to moz.build files; r=gps	2013-04-01 11:36:59 -07:00