Closed
Bug 786945
Opened 13 years ago
Closed 13 years ago
Cannot set value to <select> element
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-basecamp:+)
VERIFIED
FIXED
| blocking-basecamp | + |
People
(Reporter: rudyl, Assigned: schien)
References
Details
Attachments
(1 file)
|
1.43 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
STR
===
1. Click a <select> element (in UI test app. for example)
2. Select an option and click [OK].
Expected: the option could be set as the value of the <select>.
Actual result: UI freeze.
Error message
=====
/GeckoConsole( 1430): [JavaScript Error: "NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: '[JavaScript Error: "this._messageManager.broadcastAsyncMessage is not a function" {file: "jar:file:///system/b2g/omni.ja!/components/MozKeyboard.js" line: 69}]' when calling method: [nsIB2GKeyboard::setSelectedOption]" {file: "app://system.gaiamobile.org/js/value_selector/value_selector.js" line: 156}]
| Assignee | ||
Comment 1•13 years ago
|
||
Should use sendAsyncMessage instead of broadcastAsyncMessage, since MozKeyboard no longer uses nsIMessageBroadcaster.
Assignee: nobody → schien
| Assignee | ||
Comment 2•13 years ago
|
||
The codebase I used for testing bug 781438 doesn't grab the API change made in bug 776825. MozKeyboard should use |sendAsyncMessage| since it no longer uses the nsIMessageBroadcaster.
I've tested on the latest hg repo.
Attachment #656781 -
Flags: review?(21)
Updated•13 years ago
|
blocking-basecamp: --- → ?
Comment 4•13 years ago
|
||
Blocking as this is something that will likely happen on webpages as well.
blocking-basecamp: ? → +
Attachment #656781 -
Flags: review?(21) → review+
Comment 5•13 years ago
|
||
Comment 6•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•