In bug 143409, I mentioned that it would make it a lot easier if view-source and composer's source mode used the same specialized edit widget for both composer and view-source that allowed: - Syntax coloring based on a modifyable text-based datafile/filter for each kind of document. - Optional line numbers (based on some property to enable) - Ability for a callback function to be added for output of line number in status area - Ability to be sent to a specific line number - Basic text editor functions This would make things much easier to keep view-source and composer's plain text mode identical. Possibly this could be an extension of the XUL Editer widget that composer currently uses.
you want it, you write it.
Assignee: doron → netdemonz
Confirmed. Since view-source uses the layout engine for syntax highlighting, good luck making it editable to boot. Your best bet would be to make it be like Composer's "normal" mode. It would suffer all the same problems, of course.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: pmac → netdemonz
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
Component: View Source → View Source
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.