22262 - Display unknown tags as icons

Status: VERIFIED DUPLICATE of bug 35646

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

Description

[Michael Lowe]

Unknown tags (or tags not otherwise editable elsewhere in the editor eg.
<style>) should be displayed as icons as in 4.x.   Double clicking on such an
icon should bring up a dialog box allowing the user to edit the tag and
attributes.

Comment 1

[rubydoo123]

assigning to cmanske

Comment 2

[rubydoo123]

moving this to m16, we need to wait and get the list of the html 4.0 elements
tested from petersen and sujay.

Comment 3

[leger]

Setting the keyword all open [4.xp] bugs to 4xp.

Comment 4

[Charles Manske]

I added showing <span> and <div>. Others will follow.

Comment 5

[Charles Manske]

We really don't want to do what we do in 4.x, which is to display images
for HTML tags that aren't visible, like <span> and <div>, at least not in the
"normal" editing mode. I would like to implement a "all tags mode" which would
have specific images (or other specific generated content) for each HTML tag in 
the DTD.
The question is, should we worry about tags that aren't in the HTML DTD that we
use? Such as proprietary tags from Microsoft or older Netscape versions.
That would require help from layout to set the display type of tags it doesn't
know about (not in ua.css, I guess?) to something that would be visible.
Troy: does that sound possible?

Comment 6

[Charles Manske]

Rickg says we he can add something to the parser to help out with this.

Comment 7

[Charles Manske]

Some good comments from Matthew Thomas ([e-mail]):
Such an idea could work, provided that:
(a) the attribute has a name such as "moz-unknown", which is much less
    likely to clash with a real attribute in a future DTD than a single
    English word like "unknown" is;
(b) the "moz-unknown" attributes are *not* saved with the document, but
    are regenerated each time the document is opened. (You'd probably
    want to hide them when showing the source of the document while
    editing it, too.)

These two things would help make sure that bad stuff doesn't happen if I
happen to use an old copy of Moz Composer to edit a W3C HTML 6.1
document, in a few years time. :-)

Comment 8

[Charles Manske]

This is essentiall a dup of 35646

*** This bug has been marked as a duplicate of 35646 ***

Comment 9

[sujay]

verified in 5/8 build.