Closed
Bug 784590
Opened 11 years ago
Closed 11 years ago
No onchange event after seleted options by value selector(mozbrowser <select>)
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: iliu, Assigned: schien)
Details
(Whiteboard: [qa-])
Attachments
(1 file)
1.72 KB,
patch
|
fabrice
:
review+
|
Details | Diff | Splinter Review |
STR ==== 1. Launch Clock app or UI Test app with B2G Desktop build or on B2G device. 2. A) Clock app: a) Click right-top corner button to create an alarm. b) Click repeat, sound, snooze menu to select options. c) The value selector overlay will show up. d) Select one of the options and click [OK] B) UI Test app: a) Listen the onchange event of the any <select> first. b) Click the <select>, the value selector overlay will show up c) Select one of the options and click [OK] Actual result: - There is no onchange event after seleted options and confirmed it by value selector. Expected result: - "onchange" event should be fired after seleted options and confirmed it by value selector. Note: There is no way to update the result of selection.
Comment 1•11 years ago
|
||
Vivien, is that because of how the vkb is implemented or is that a bug with the DOM implementation?
Comment 2•11 years ago
|
||
Is this a dup of bug 781438?
Assignee | ||
Comment 3•11 years ago
|
||
In b2g/chrome/content/forms.js, the selected option is changed via javascript, which will not generate onchange event. We need to create a onchange event mannually.
Assignee: nobody → schien
Assignee | ||
Comment 4•11 years ago
|
||
Onchange event is not fired due to selected option is changed via javascript in b2g/chrome/content/forms.js. We need to manually create a DOMEvent and fire it on <select> element.
Attachment #657528 -
Flags: review?(fabrice)
Updated•11 years ago
|
Attachment #657528 -
Flags: review?(fabrice) → review+
Updated•11 years ago
|
Whiteboard: [qa-]
Comment 6•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/6300a954d434
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•