Closed
Bug 810746
Opened 12 years ago
Closed 12 years ago
[keyboard]Cannot delete the text in a text field with Chinese Pinyin Keyboard
Categories
(Firefox OS Graveyard :: Gaia, defect)
Firefox OS Graveyard
Gaia
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: xyuan, Assigned: xyuan)
Details
(Whiteboard: [label:Keyboard & IME])
Attachments
(1 file)
11 bytes,
text/plain
|
timdream
:
review+
vingtetun
:
approval-gaia-v1+
|
Details |
## Repro 1. enable Pinyin keyboad in keyboard settings 2. focus a text field and switch to the Pinyin keyboard 3. input any text to the text field 3. click the backspace key to delete the text inputed ## Expected: The text in the text field is deleted. ## Actual: No text is deleted.
Assignee | ||
Updated•12 years ago
|
Whiteboard: [label:Keyboard & IME]
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → xyuan
Assignee | ||
Comment 1•12 years ago
|
||
The pull request was sent: https://github.com/mozilla-b2g/gaia/pull/6135
Comment 2•12 years ago
|
||
Chinese Pinyin IME is not in the scope of v1, but we would have to keep maintain it (without conflicting with shipping product) until product branch is created. [Approval Request Comment] Bug caused by (feature/regressing bug #): Bug in jspinyin User impact if declined: Chinese pinyin IME will be broken when step STR is used Testing completed: yes? Risk to taking this patch (and alternatives if risky):
Attachment #680522 -
Flags: review+
Attachment #680522 -
Flags: approval-gaia-master?(21)
Updated•12 years ago
|
Component: Gaia::System → Gaia
Comment 3•12 years ago
|
||
Comment on attachment 680522 [details] Github https://github.com/mozilla-b2g/gaia/pull/6135 one liner that fix a file that won't be used in production. a=me.
Attachment #680522 -
Flags: approval-gaia-master?(21) → approval-gaia-master+
Assignee | ||
Updated•12 years ago
|
Keywords: checkin-needed
Comment 4•12 years ago
|
||
https://github.com/mozilla-b2g/gaia/pull/6135
Device: Unagi Build: 20130113070202 Does not reproduce on this device as option is unavailable.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•