126447 - JSP taglib xml element rearranged when loaded into composer

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, enhancement)

Description

[John Maline]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204
BuildID:    2002020406

Other bugs (101917, 59985) address problems with <@ ... @> tags in trying to
edit JSP files.  I've run across another interesting problem.

I've got a JSP file I tried to load into composer.  In addition to the problems
with "<" -> "&lt;" I found some taglib elements rearranged.

It'll be the case that Struts taglib elements, for example, can appear where
HTML tags don't normally show up (but I don't know the spec sufficiently to know
if it's illegal - just a guess).  Between outside of any <tr> element inside a
table, for example.  I don't know if this is what freaks out composer.

Additionally, there was an XML open/close element set that surrounded a table. 
On loading, the close element was moved to immediately after the open.  They
displayed in the normal "yellow box" symbols that unknown tags use.

Reproducible: Always
Steps to Reproduce:
1.Load JSP file into composer
2.View HTML to see damage

Comment 1

[John Maline]

Attachment: Pre - the JSP file before loading into composer

Comment 2

[John Maline]

Attachment: Post - after loading into composer and saving

Comment 3

[Kathleen :Brade]

dup

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

Comment 4

[sujay]

verified.

Comment 5

[John Maline]

I don't think this is a dup of 101917.  I mention it as a related bug in my 
description, but it doesn't mention the symptom I'm seeing.  I guess I wasn't 
clear, including lots of extraneous material in my report.

What I'm trying to report here is the undesired movement of XML taglib elements 
by the editor.

101917 appears to be focussed on a completely different symptom, the inability 
to express the pseudo-elements "<@ ... @>" used by JSP.

My attachments show both symptoms, I should have given a clearer indication of 
what I'm reporting.  The <logic:present> </logic:present> tags were moved, and 
that is undesireable.  Others were also, but that's one example.

Comment 6

[Kathleen :Brade]

Can you provide a smaller testcase that exhibits only the rearranging issue?
Thanks!
akkana--do you want this bug since it's related to other bugs on your plate?

Comment 7

[John Maline]

Attachment: pre - simplified JSP page before loading into composer

As requested, here's a simplified example.  Here's the pre-edit state.	I do
have one <%...%> tag that gets munged, but that's not the real report.

The real problem is the rearrangement of the <logic:present> and
<logic:iterate> start and end tags.

This replaces attachment 70328 [details], but I don't have permissions to obsolete it.

Comment 8

[John Maline]

Attachment: post - simplified JSP after loading/saving from composer

Here it is after composer gets through with it.  Note the rearrangement of
<logic:present> and <logic:iterate>.

Comment 9

[Kathleen :Brade]

reassign to new account

Comment 10

[Mike Cowperthwaite]

*** Bug 186034 has been marked as a duplicate of this bug. ***

Comment 11

[Robert Kaiser]

MASS-CHANGE:
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 12

[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