Closed
Bug 335484
Opened 19 years ago
Closed 19 years ago
insertHTML doesn't actually insert the HTML
Categories
(Core :: DOM: Editor, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: davidmstone, Assigned: mozeditor)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
3.48 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060425 Minefield/3.0a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060425 Minefield/3.0a1
Within the past week or so, calling execCommand("insertHTML"...) has stopped working the way that you'd expect it to. When passed a valid HTML string, it looks like the editor is completely ignoring the outermost element. The odd part is that execCommand returns true, even though the HTML wasn't inserted. So, for instance, if you call execCommand("insertHTML", false, "<b>this text should be bold</b>"); the text will show up in the midas editor, but won't be bold.
Reproducible: Always
Steps to Reproduce:
Call execCommand("insertHTML"...) with valid HTML.
Actual Results:
The HTML doesn't get inserted, or gets incompletely inserted.
Expected Results:
The entire HTML string is inserted into the editor.
Reporter | ||
Comment 1•19 years ago
|
||
Here's a testcase. This pretty clearly shows what's wrong.
Comment 2•19 years ago
|
||
Confirmed.
Maybe the fix for bug 333063 could fix it. Please try with the 2006-04-26 trunk build?
Status: UNCONFIRMED → NEW
Depends on: 333063
Ever confirmed: true
Flags: blocking1.9a1?
Keywords: regression,
testcase
Reporter | ||
Comment 3•19 years ago
|
||
Beeyooteeful. :) Works again.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•18 years ago
|
Flags: blocking1.9a1?
You need to log in
before you can comment on or make changes to this bug.
Description
•