Closed Bug 141338 Opened 22 years ago Closed 14 years ago

Raw HTML text editor should save without trying to repair changes

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: hwaara, Unassigned)

References

Details

Reproducible steps:

1. Open a HTML page.
2. Click on the HTML source editor mode tab.
2. Attempt to remove the <head>...</head> section, and then hit "Save".

Result: editor re-adds the head section.
Expected result: it should save my change.

If I go to the raw HTML source mode, I expect any changes I make to really take
place. If I screw the whole document over, and then click "Save", the editor
should just save it as plain text without trying to validate it.

Of course, if I go back to WYSIWYG mode, it's understandable if the editor wants
to repair my document in order to view/edit it, but when I am in the raw editor,
I just want it to save without any hassle.
This is composer...
Assignee: kin → syd
Component: Editor: Core → Editor: Composer
Charley, how are we doing output from the source view?  Are we just serializing
the source to plaintext, or do we generate a document somehow and then serialize
the html?
Sorry, this is not how it currently works. We never save "raw text", just HTML.
HTML Source view is simply an HTML output to a textarea; we must reconvert to
HTML to be able to save. I'd say for 90% of users, this is a *very good thing* to
have their HTML source repaired!
This request is another example of what could be done when we have multiple 
editors and a separate full plaintext editor to use for source editing (see
bug 69329).
Status: NEW → ASSIGNED
Depends on: 69329
Target Milestone: --- → Future
I'm guessing Charley meant to take this, since he marked it assigned ...
reassigning to him.

Since we have the textarea, wouldn't it be easy just to get its output and dump
that directly?  (Easier than converting back to a dom and getting html output ...)
Assignee: syd → cmanske
Status: ASSIGNED → NEW
I agree with Akkana.  Besides, what's the point of this view if what I see will
not necessarily be what I save? That's just confusing to me.
Please, I second this.  Composer 'corrects' many other things too making it
unusable as an editor for many projects.  It always seems to switch the
background from a dynamic link to a local file.

If I had a straight publish as-is feature, I could use it to fix up php too.
Product: Browser → Seamonkey
*** Bug 225667 has been marked as a duplicate of this bug. ***
Assignee: cmanske → nobody
QA Contact: sujay → 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: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.