Closed
Bug 906614
Opened 11 years ago
Closed 11 years ago
Change Gaia keyboard app to use the new surrouding text related functions/event in IME WebAPI
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rudyl, Assigned: lchang)
References
Details
(Whiteboard: [3rd-party-keyboard][ft:system-platform])
Since bug 899999 has landed, we need to change the implementation of latin IME engine in Gaia keyboard app to use onsurroundingtextchange instead of tracking the current value in app itself.
|
Reporter | |
Updated•11 years ago
|
Blocks: 3rd-party-keyboard
|
|
Reporter | |
Updated•11 years ago
|
blocking-b2g: --- → koi?
Whiteboard: [ft:system-platform], [Sprint: 3]
|
Assignee | |
Updated•11 years ago
|
Assignee: nobody → lchang
Status: NEW → ASSIGNED
|
||
Comment 1•11 years ago
|
||
Not blocking because this not required for v1.2 and does not provide new functionalities (the interaction will be better though).
blocking-b2g: koi? → -
|
|
||
Updated•11 years ago
|
Whiteboard: [ft:system-platform], [Sprint: 3] → [3rd-party-keyboard][ft:system-platform]
|
||
Comment 4•11 years ago
|
||
This bug is the refactoring to allow built-in keyboard to use API to get current keyboard status. It won't affect existing function and behavior. Not a blocker for v1.3. Move to Madai.
blocking-b2g: 1.3? → madai?
|
|
Reporter | |
Comment 6•11 years ago
|
||
It seems the new keyboard that lives test_apps/demo-keyboard already leverages the new API and listen to "surroundingtextchange" event and we don't have a plan to update the current built-in keyboard app.
Close this for now.
Status: ASSIGNED → RESOLVED
blocking-b2g: 1.4? → ---
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•