404320 - FormatBlock doesn't work correctly will break existing Midas implemenations

Status: RESOLVED FIXED

(Core :: DOM: Editor, defect, P3)

Description

[spam]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9

The Midas FormatBlock command doesn't work in the current Firefox 3 branch. I attached a test case that works perfectly fine in Firefox 2 but fails in the current implementation. The FormatBlock command is also not compatible with other browsers like IE, Safari, Opera.

Check this bug for details on the compatibility:
https://bugzilla.mozilla.org/show_bug.cgi?id=316544

Reproducible: Always

Steps to Reproduce:
1. Open attached test case in latest nightly build.
2. Place cursor/caret inside on of the editable elements.
3. Click one of the formatblock links.
4. Observe that the block doesn't get formatted correctly.
Actual Results:  
The code remains the same.

Expected Results:  
One of the elements that the caret was placed in should have been converted into a div element.

Comment 1

[spam]

A follow up, it seems that the current implementation can only handle h1-h6,p,pre,address where the previous implementation could handle most of the block elements like div, code, dt, dl, samp etc.

It seems to be that it checks the format against the gMidasParamTable list. This should be extended with all block element.

http://lxr.mozilla.org/seamonkey/source/content/html/document/src/nsHTMLDocument.cpp#4228

This bug breaks existing editors like TinyMCE of FCKEditor those editors are used in the most popular CMS and Blog systems out there. So I think this is at least a major bug.

Comment 2

[Samuel Sidler (old account; do not CC)]

I can reproduce this, but I'm not sure if it's intended since I don't know enough about Midas.

Moving to Core and requesting blocking, but not confirming.

Comment 3

[Mike Beltzner [:beltzner, not reading bugmail]]

peterv: can we get your weigh-in here?

Comment 4

[Peter Van der Beken [:peterv]]

Attachment: v1

Yeah, we started being more restrictive (FF2 accepted any tag name), but we're missing some tag names that IE and Safari accept. Note that HTML5 doesn't allow <div> at all, so we'll be incompatible with that.
Anyway, trivial to fix. I'll attach a mochitest too.

Comment 5

[Peter Van der Beken [:peterv]]

Attachment: v1

Comment 6

[Peter Van der Beken [:peterv]]

Attachment: Mochitest

Comment 7

[Peter Van der Beken [:peterv]]

Comment on attachment 289978 [details] [diff] [review]
v1

Simple fix to make our designMode/contentEditable editing API more compatible with IE and Safari.

Comment 8

[Mike Beltzner [:beltzner, not reading bugmail]]

Comment on attachment 289978 [details] [diff] [review]
v1

a=beltzner for drivers