*** Bug 183540 has been marked as a duplicate of this bug. ***
"composer" == "editor:composer", not "editor:core"
Assignee: jfrancis → syd
Component: Editor: Core → Editor: Composer
confirming; I see this also when changing the html content (as opposed to editing a script)--just type "abc" between the <br> tags
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: dataloss, nsbeta1
OS: Windows 2000 → All
Hardware: PC → All
Assignee: syd → composer
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: normal → critical
Workaround for reporter until we fix the bug: remove all occurences of " from attribute values. Example: "service" I confirm the bug. The reparsing of the html content chokes on this attribute, expanding it to its character value and hence closing the attribute data.
not all JS is being corrupted, it seems to be specific to this type of case: <a onmouseover="jsFunc('<ul><li>..."service" and "results".</li>', event)" onmouseout="couic()" onclick="return false"> text to be shown here </a>
btw bug 68167 still seems to be fixed
Composer triage team: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
WFM with trunk build 20030428
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
reopening bug I don't believe this is fixed. The content at the url above has changed. It now uses " entity where it once had double-quote ("). Removing url (http://jmreymond.free.fr/tommy/jobsbody.html). Please see comment 8 for a snippet of a still broken example.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
the page http://jmreymond.free.fr/tommy/jobsbody.html has no changes since the bug is opened.
No activity since November 2004, no comment since May 2003. I don't use Composer myself so I cannot validly check this bug. Is anyone still seeing it on SeaMonkey 2.0a1pre? Unless someone replies within, say, a week or so I suppose this bug will be resolved INCOMPLETE or WORKSFORME.
Ten days gone, no reply, resolving as INCOMPLETE
Status: REOPENED → RESOLVED
Last Resolved: 15 years ago → 10 years ago
Resolution: --- → INCOMPLETE
This is almost certainly still a bug but I don't have a recent Seamonkey build to test this against. Why the rush to resolve an old bug? Daniel--can you confirm (reopen bug)?
(In reply to comment #16) > This is almost certainly still a bug but I don't have a recent Seamonkey build > to test this against. Why the rush to resolve an old bug? An effort has been recently launched (by Kairo, the SeaMonkey Council head) to "decide" old Mozilla Suite bugs, decide whether or not they still apply to SeaMonkey, and update them accordingly. Would you rather these bugs should remain unresolved but unattended, forgotten, falling into oblivion? If it's still a bug, it should be Confirmed and if possible worked on; if it isn't, it should get Resolved and maybe even Verified. > Daniel--can you confirm (reopen bug)? See Daniel's comment #11.
You need to log in before you can comment on or make changes to this bug.