101917 - Composer should `color` <? and <% tags (PHP/JSP/...)

Status: NEW

(SeaMonkey :: Composer, enhancement)

Description

[Michael Kolmodin]

As of today, the composer cannot handle tags containing JSP/PHP. Examples
might include <fs:aTag arg="argument"> or 
<input type="text" sixe="<? print $size ?>" >. In both cases, the tags should
propably be shown as some kind of red box indicating that the tag is "active"
but without any attempt to render it

Comment 1

[Boris Zbarsky [:bzbarsky]]

Compositor is not the same as Editor:Composer.  Please read the component
descriptions. 

duplicate of "JSP/PHP files corrupted by composer:  '<%' and '%>' <?php ?>"

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

Comment 2

[Boris Zbarsky [:bzbarsky]]

Um.  I should read the entire bug befor dupping.  Reopening

Comment 3

[Boris Zbarsky [:bzbarsky]]

Over to correct component.

Comment 4

[Akkana Peck]

Accepting -- it would be great to show these as tags, with some provision to
edit them easily.  Cc Kathy and Charley in case they have ideas. 
Future/helpwanted for now, but may pull back in if 59985 gets fixed.

Comment 5

[Akkana Peck]

I just noticed that the bug was assigned to syd, not me, so I should have
reassigned before accepting.

Comment 6

[Kathleen :Brade]

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

Comment 7

[Kathleen :Brade]

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

Comment 8

[Kornel Szabo]

the problem is, that it worked with the 0.9.7 version....but then it broke
somehow :-(

Comment 9

[Markus Jung]

I think it is not necessary to show the tags between <? and ?>. of corse it
would be good if it is possible to see and edit it in the html-source view.

but the main problem at the moment is, that the tags are deleted without any
kind of alert. that is very dangerous if somebody is working with composer,
without knowlege about this problem. it can destroy the work of hours...

the editor should just leave the tags (which he not know) were they are. For me,
it has a high priority.

Comment 10

[Akkana Peck]

Markus: bug 59985 covers the corruption of the tags by the parser.  This bug is
for composer showing them somhow, once the parser is fixed to pass the tags to us.

Comment 11

[Charles Manske]

The parser is supposed to label all non-standard tags with "_moz-userdefined" 
attribute so Composer displays a yellow icon with "?" in it, but only in "Show
All Tags" edit mode. We normally show nothing in "Normal" mode.
If we need to show a specific tag in Normal mode, the parser would have to add a 
different attribute that could be used to show an icon by a new style rule in 
EditorOverride.css (rules here show all the time.)

Comment 12

[Akkana Peck]

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

Comment 13

[timeless]

i'm using color in a loose sense, I don't care if we take color to mean putting
an image before the content, or literally coloring, or outlining.

Comment 14

[Owen Watson]

I've just downloaded 1.2a, and it's still here. I don't think any editor should
mangle code without your express permission. Mozilla would be great for a CMS
once this bug is fixed.

Comment 15

[Akkana Peck]

Owen: I suggest you make your comments in the parser bug that this one depends
on.  Composer can't do anything until the parser is fixed to preserve those tags.

Comment 16

[Marco Brandizi]

Still there in 1.6... So sad... :-(

Comment 17

[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 18

[mail]

I confirm that this bug exists with Seamonkey 2.0b1.

Simple php code like 

 <?php echo $count;?>  &nbsp;visitors this month

has the php part removed by Composer. 

<!-- <?php echo $count;?> --> will be retained by Composer but is useless as it is ignored by the browser.

Laurie