Closed Bug 203259 Opened 23 years ago Closed 16 years ago

Does not save some WWW pages correctly.

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: Darryl, Unassigned)

Details

(Keywords: helpwanted)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 I use a Meta language called WML - Web Meta Language. THis language allows me to compile my pages on a WWW site but the use of #INCLUDE, #USE, Custom Tags, Embedded perl etc. I occasionally need edit in Composer for the content rather than for paramaters for the includes. When I do this I need to tell it to "RETAIN ORIGINAL SOURCE FORMATTING" else it will totally change the formatting of my document. Even when I say RATAIN, I get other corruptions - such as the first line being added saying that this is HTML, Any single TAGS that I have defined (such as <FOOTER> which includes my standard footer) now have a corresponding close tage (such as </FOOTER>. Any tags that the application does not understand should be left unmodified. The application does not add a closing tag for <BR> so why should it do it for other tags? Please remember that not all HTML editing is done on PURE HTML pages. An editor should only edit a part of a docuemnt that I cange. If I want to edit a PHP document it should be able to di it Reproducible: Always Steps to Reproduce: 1. 2. 3.
Whiteboard: DUPEME
related to Bug 59985
Future; Composer is for pure html today (maybe some day it will do more)
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Keywords: helpwanted
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → Future
Product: Browser → Seamonkey
Assignee: composer → nobody
Status: ASSIGNED → NEW
QA Contact: chrispetersen → composer
Target Milestone: Future → ---
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
Closed: 16 years ago
Resolution: --- → EXPIRED
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.