103574 - The editor should accept <tag/> format and attributes without value

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Jarmo]

I've an application that uses html templates with a twist. It has some own tags,
and some of them do not have any body: <tag arg1 arg2="with value"/> note the
"/>" termination. When editing those files mozilla rewrites them as: <tag
arg1="" arg2="with value"></tag> :which breaks my application :-(

Note _two_ errors: 
1) mozilla refuses to accept arguments _without_ values (which is legal html)
2) It rewrites those "xml styled" tags.

point 1 is actually a _bug_, but as most readers ignore unexpected and empty
values it does not matter.

Comment 1

[Christopher Hoess (gone)]

Jarmo: adding your own tags and attributes is not "legal HTML", period.  If this
is a question of adding arguments to <input>, for instance, I recommend using
the "class" attribute, which can take the form of a space-separated list of
arguments.  I don't think Mozilla supports (in browser) true SGML attribute
minimization yet.

See bug 94284 for point 2.

Comment 2

[Jarmo]

> adding your own tags and attributes is not "legal HTML", period.  If this

According to point 1) (I assume). I do not want to start a flame war (and after
all this is enhandement request, not a bug report!).

The question was not of _own_ HTMLs, what of:

<table><tr><td nowrap>My data that does not wrap</td></tr></table>

Prefectly legal HTML 3, but the editor rewrites it to:

<table><tr><td nowrap="">My data that does not wrap</td></tr></table>

Note the change in _nowrap_.

Well nuff about this.

Comment 3

[Jarmo]

Changed subject to better describe the bug.

Comment 4

[Kathleen :Brade]

Akkana--is this a duplicate bug?  There are actually two issues here:
  * termination of tag: <tag/> vs <tag></tag>
  * attribute not emitted correctly:  <tag foo> vs <tag foo=""> vs <tag foo=foo>
Do we have bugs for both of these?  Which issue should this bug cover?

Finally, who should this bug be reassigned to?  Dom To Text Conversion?

Comment 5

[Akkana Peck]

There is definitely a bug for <tag foo=""> vs <tag foo=foo>, though I don't know
the number offhand (probably in the category DOM-text conversion, or possibly
html parser).

As for <tag />, the XML serializer will do that, and I believe there's a bug
filed for being able to edit and output xhtml (which would have to go through
the xml serializer), but currently we only support normal html, through the html
serializer.

Comment 6

[Kathleen :Brade]

reassign to new placeholder

Comment 7

[Ted Shaneyfelt]

The serializer bug (<br /> vs <br>) is #55313. 

Comment 8

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420