Opened 15 years ago

Closed 11 years ago

#3607 closed defect (wontfix)

dijit Editor doesn't show any further inputs if bullets are overwritten

Reported by: guest Owned by: Jared Jurkiewicz
Priority: high Milestone: future
Component: Editor Version: 0.9
Keywords: Cc: [email protected]
Blocked By: Blocking:

Description (last modified by bill)

Using Firefox 2.0 on dijit/tests/test_Editor.html and the bottom section of dijit/tests/test_RichText.html it is possible to stop the area showing any further input if you select the entire set of bulleted points and start typing.

Using Firebug I found that the content of the Iframe body element was reduced to a single <ul/> element.

Change History (9)

comment:1 Changed 15 years ago by bill

Milestone: 0.9

comment:2 Changed 14 years ago by liucougar

Resolution: fixed
Status: newclosed

(In [9959]) fixes #3607, #3736 and #3979

comment:3 Changed 14 years ago by guest

Resolution: fixed
Status: closedreopened

There is still a Firefox bug if you select all of the bullets on the list and start typing that it wont show any input until you hit backspace.

It occurs on both the RichText? and Editor test pages in the nightly build and on my latest checkout. : Bottom box, select both of the numbered items and start typing : Both boxes, select both of the sets of bullets completely and start typing

comment:4 Changed 14 years ago by liucougar

Milestone: 1.01.1

uhm, this seems to be a firefox bug, punt for now

comment:5 Changed 14 years ago by dylan

Milestone: 1.11.2

mass move of editor issues to 1.2.

comment:6 Changed 13 years ago by bill

Description: modified (diff)
Milestone: 1.2future

Unfortunately bug persists in FF3 and happens even when using contentEditable div instead of iframe.

I don't see how to fix it though.

Only seems to happen if the bullet list is at the end?

The good news is that if you move the cursor around you can start typing again.

Punting on this until we have a volunteer to work on it.

comment:7 Changed 12 years ago by bill

Owner: liucougar deleted

comment:8 Changed 12 years ago by Douglas Hays

Owner: set to Jared Jurkiewicz
Status: reopenednew

comment:9 Changed 11 years ago by Jared Jurkiewicz

Resolution: wontfix
Status: newclosed

I cannot figure out a way to work around this browser issue. You can't really trap the key as it needs to flow through to actually delete the content, and once that happens, it's hard to tell where exactly you are, then move and resume the typing. I, frankly, am not sure how to resolve this. I'll try a couple more things, but for now I'm just marking it as 'wontfix'

Note: See TracTickets for help on using tickets.