Open Bug 58730 Opened 25 years ago Updated 5 years ago

(Color) Syntax Highlighting in HTML Source Mode (Composer-specific)

Categories

(SeaMonkey :: Composer, enhancement)

Product:
SeaMonkey
Component:
Composer
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: ptrourke, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: helpwanted)

Would be a nice feature for Moz 1 or NS6.1
confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: other → All
Hardware: PC → All
Is this related to (or even a dup of) bug 52154?
> Is this related to (or even a dup of) bug 52154? > Make a pref for view source coloring Yep, looks like it. Sorry, but none of my search terms brought up 52154.
accepting this bug for beppe and setting to milestone future; add "helpwanted" I don't think this is the same as bug #52154 since the Composer HTML Source mode is actually an editor whereas the view source window is static (and implemented completely differently).
Status: NEW → ASSIGNED
Keywords: helpwanted
Summary: Syntax Highlighting in HTML Source Mode → Syntax Highlighting in HTML Source Mode (Composer-specific)
Target Milestone: --- → Future
Assumedly this would be implemented in such a way as to make XML/CSS/XSLT/JS/etc editor syntax highlighting fairly easy.
*** Bug 57606 has been marked as a duplicate of this bug. ***
I wish the very common 4 character sequence ampersand ell tee semi were *all* hilited (highlighted ?) in the same color in View Source. Right now, the ampersand is black as if it were ordinary text (which it is not), and the other 3 characters are red. Responding to brade@netscape.com: I fail to see why ``view source'' on the browser side is different from ``HTML source mode'' in the composer. Why re-invent the wheel ?
I agree with dcary@BrunswickOutdoor.com Why do you need to reinvent the way the HTML source is highlighted. Vim and other editors do syntax highlighting without any ado. Another feature that should be included with Navigator is the ability to select which editor should be used to edit HTML files. I use vim, someone else might like Notepad (god save that person!)
The lack of this feature is making composer very frustrating/cumbersome to use. Composer is one of the four main parts of Mozilla (browser, mail/news, composer and address book) and should the mess it is now. I suggest to increase the Priority and Target Milestone of this highly visible module - but the decision is not mine to make (hence the "suggestion").
-->cmanske
Assignee: beppe → cmanske
Status: ASSIGNED → NEW
*** Bug 98373 has been marked as a duplicate of this bug. ***
spam composer change
Component: Editor: Core → Editor: Composer
*** Bug 60437 has been marked as a duplicate of this bug. ***
Speaking as a user, it would be nice to see this in 1.0. Since view source (where syntax highlighting really doesn't matter much - it's not like you debug anything in view source) has this feature and composer (where it's a great help to the user) doesn't, it will smell like a bug rather than a non-feature.
*** Bug 149983 has been marked as a duplicate of this bug. ***
*** Bug 153537 has been marked as a duplicate of this bug. ***
*** Bug 163699 has been marked as a duplicate of this bug. ***
*** Bug 169122 has been marked as a duplicate of this bug. ***
*** Bug 171310 has been marked as a duplicate of this bug. ***
Is there any new processing? The Browser can show source with syntax highlighting,but the Composer cannot edit source with syntax highlighting. I want to know if the two functional modules are relative.
Depends on: 69329
*** Bug 207450 has been marked as a duplicate of this bug. ***
Guys i don't know if i´m making a stupid remark, but komodo by activestate.com wich is based on mozilla has sintax coloring, maybe you guys could have a look at the code? Also it would be nice if we could (as in komodo) define wich color we like to use.
CCing glazman@netscape.com, as I think he should be aware of a Composer bug with 21 votes (currently ranked #4) Prog.
*** Bug 210026 has been marked as a duplicate of this bug. ***
*** Bug 213518 has been marked as a duplicate of this bug. ***
Almost all 11 dupes of this bug included the words "Color" and "Source". Would it be possible to add them to the summary in order to prevent more dupes? Thanks, Prog.
Summary: Syntax Highlighting in HTML Source Mode (Composer-specific) → (Color) Syntax Highlighting in HTML Source Mode (Composer-specific)
I'm on it.
Assignee: cmanske → daniel
Fix attached to bug 47040 and solving also this bug.
Product: Browser → Seamonkey
Depends on: 47040
*** Bug 361505 has been marked as a duplicate of this bug. ***
This bug is pending since year 2000... When will this feature be available ? perhaps in 2007 ?
Syntax coloring is already available in the Mozilla Suite and SeaMonkey browsers (suggesting that some code to implement it has already been written), I am very surprised that it is not available in the Composer Source tab. It definitely would make the Composer Source tab more readable, and also would facilitate learning HTML. I hope it is implemented soon.
Assignee: daniel → nobody
Priority: P3 → --
QA Contact: sujay → composer
Target Milestone: Future → ---
I use SeaMonkey 2.26.1. The bug is still here (after 6 years). Please implement Syntax highlighting in SeaMonkey. Without this feature SeaMonkey is useless (as NVU and KompoZer).
(In reply to Norbert from comment #33) > I use SeaMonkey 2.26.1. The bug is still here (after 6 years). > Please implement Syntax highlighting in SeaMonkey. > > Without this feature SeaMonkey is useless (as NVU and KompoZer). It's not after 6 years, it's after 14 years !!!
Bug still exists in SeaMonkey 2.46.

SeaMonkey Composer 2.53.5.1 - there is still no code syntax highlighting in the application. 20 years.

You need to log in before you can comment on or make changes to this bug.