Closed Bug 796365 Opened 12 years ago Closed 12 years ago

Contenteditable doesn't bring up keyboard

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect, P1)

defect

Tracking

(blocking-basecamp:+, firefox18 fixed, firefox19 fixed)

VERIFIED FIXED
B2G C2 (20nov-10dec)
blocking-basecamp +
Tracking Status
firefox18 --- fixed
firefox19 --- fixed

People

(Reporter: ghtobz, Assigned: xyuan)

References

()

Details

(Keywords: smoketest, Whiteboard: [label:Keyboard & IME])

Attachments

(1 file)

[GitHub issue by lsblakk on 2012-06-20T17:19:39Z, https://github.com/mozilla-b2g/gaia/issues/1837]
On a Nexus S that was just flashed yesterday (06-19-2012) when I run the UI Tests app and try the Keyboard tests, go to the Contenteditable section and touch the "Edit Me!" text I get a cursor but the keyboard does not come up for editing.
[GitHub comment by timdream on 2012-06-21T03:08:39Z]
At first I think it's related to https://bugzilla.mozilla.org/show_bug.cgi?id=766549 but that bug is not landed yet! 

@vingtetun @RudyLu
Assignee: nobody → xyuan
I am not sure this is blocking-basecamp+.
Nominate this as blocking-basecamp?
blocking-basecamp: --- → ?
Attachment #680556 - Flags: review?(21)
Attachment #680556 - Flags: approval-gaia-master?(21)
I guess that patch doesn't work for the designMode document case, right?
blocking-basecamp: ? → +
Keywords: smoketest
Priority: -- → P1
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "remaining P1 bugs not already milestoned for C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #5)
> I guess that patch doesn't work for the designMode document case, right?

Yes, not for the designMode. Thanks for providing the test cases. I think we need another bug to fix the designMode as way to deal with it is a little different.
Bug 811177(https://bugzilla.mozilla.org/show_bug.cgi?id=811177) was created to track the designMode issue.
See Also: → 811177
Comment on attachment 680556 [details] [diff] [review]
Treat contenteditable as a special text field to bring up the keyboard

No need for gaia approvals for blocking-basecamp bugs.
Attachment #680556 - Flags: review?(21)
Attachment #680556 - Flags: review+
Attachment #680556 - Flags: approval-gaia-master?(21)
Will push in a minute.
Status: NEW → ASSIGNED
Keywords: checkin-needed
Component: Gaia → General
https://hg.mozilla.org/mozilla-central/rev/22360b84eb87
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Attachment #680556 - Attachment is obsolete: true
Comment on attachment 680556 [details] [diff] [review]
Treat contenteditable as a special text field to bring up the keyboard

Recover the patch that was marked as obsolete by mistake.
Attachment #680556 - Attachment is obsolete: false
Component: General → Gaia::Keyboard
QA Contact: wachen
http://0rz.tw/uFCwf is created for people to access http://people.mozilla.org/~mwargers/tests/contenteditable/contenteditable.htm

http://0rz.tw/4xy5I is created for people to access http://people.mozilla.org/~mwargers/tests/contenteditable/designmode.htm

I verified it in 2013-01-20-07-02-02 pvt nightly b2g18 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: