If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Cannot enter text into a empty block with contenteditable on Android

RESOLVED WORKSFORME

Status

()

Firefox for Android
Keyboards and IME
RESOLVED WORKSFORME
3 years ago
a year ago

People

(Reporter: Sam, Assigned: esawin)

Tracking

({reproducible, testcase})

Trunk
ARM
Android
reproducible, testcase
Points:
---

Firefox Tracking Flags

(firefox36 affected, firefox37 affected, firefox38 affected, firefox39 affected, fennec+)

Details

(URL)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36 OPR/27.0.1689.76

Steps to reproduce:

With the HTML:

<div contenteditable="true">
    Try type in the box below:
    <p><br /></p>
</div>

It's impossible to enter any text into the empty <p> tag. It's the same for all the block level elements I've tested.

Demo HTML: http://jsfiddle.net/50hhsdbk/
Video example: https://dl.dropboxusercontent.com/u/56830471/screen-recording_20150311-223049.mp4


Actual results:

The cursor is moved out of the block to the nearest previous text


Expected results:

The cursor should remain inside the block and the text should be entered into it
(Reporter)

Updated

3 years ago
OS: Linux → Android
Hardware: x86_64 → All

Updated

3 years ago
Status: UNCONFIRMED → NEW
tracking-fennec: --- → ?
status-firefox36: --- → affected
status-firefox37: --- → affected
status-firefox38: --- → affected
status-firefox39: --- → affected
Component: Text Selection → Keyboards and IME
Ever confirmed: true
Keywords: reproducible, testcase
Hardware: All → ARM
Version: Firefox 37 → Trunk

Updated

3 years ago
(Assignee)

Updated

3 years ago
Assignee: nobody → esawin

Updated

3 years ago
tracking-fennec: ? → +
(Assignee)

Comment 1

a year ago
WFM, must have been resolved in the meanwhile.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.