Closed Bug 471722 Opened 15 years ago Closed 15 years ago

Plaintext editor redo handling code looks for incorrect type of bogus node

Categories

(Core :: DOM: Editor, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9.2a1

People

(Reporter: graememcc, Assigned: graememcc)

Details

(Keywords: fixed1.9.1, Whiteboard: [fixed1.9.1b3])

Attachments

(3 files, 4 obsolete files)

Attached patch Trivial fix (obsolete) — Splinter Review
From http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/editor/libeditor/text/nsTextEditRules.cpp&rev=HEAD&mark=1.211, revision 1.73 (which seems to correspond to bug 16905) the "bogus node" type was changed from a <div> to <br>.

When checking to see if a bogus node reappeared after redo, we're still looking for divs...
Attachment #354977 - Flags: superreview?(peterv)
Attachment #354977 - Flags: review?(peterv)
Comment on attachment 354977 [details] [diff] [review]
Trivial fix

Sigh. I guess we don't really know how to test this?
Attachment #354977 - Flags: superreview?(peterv)
Attachment #354977 - Flags: superreview+
Attachment #354977 - Flags: review?(peterv)
Attachment #354977 - Flags: review+
Attached patch Patch with possible mochitest (obsolete) — Splinter Review
Would something like this be a suitable test?

It fails against current trunk, after the redo, the textbox's value = "\n" rather than "".
Attachment #355475 - Flags: superreview?(peterv)
Attachment #355475 - Flags: review?(peterv)
Comment on attachment 355475 [details] [diff] [review]
Patch with possible mochitest

Er, the second patch shouldn't need sr, as I already have it from the first patch, and this is just a review request for the test.
Attachment #355475 - Flags: superreview?(peterv)
Might as well try to get the fix in for baking. The test can follow.
Assignee: nobody → graememcc_firefox
Status: NEW → ASSIGNED
Attachment #360975 - Attachment mime type: application/octet-stream → text/plain
Keywords: checkin-needed
Whiteboard: Please checkin "hg export for checkin"
Attached patch Mochitest (obsolete) — Splinter Review
Attachment #355475 - Attachment is obsolete: true
Attachment #360977 - Flags: review?(peterv)
Attachment #355475 - Flags: review?(peterv)
Attachment #360975 - Attachment is patch: true
http://hg.mozilla.org/mozilla-central/rev/6ebf4afe67d2
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite?
Keywords: checkin-needed
Resolution: --- → FIXED
Whiteboard: Please checkin "hg export for checkin"
Target Milestone: --- → mozilla1.9.2a1
Attachment #360977 - Flags: review?(peterv) → review+
Keywords: checkin-needed
Whiteboard: please check in mochitest patch
Attachment #360975 - Attachment description: hg export for checkin → hg export for checkin [Checkin: Comment 6]
Attachment #354977 - Attachment is obsolete: true
Attachment #360977 - Attachment is obsolete: true
Comment on attachment 362309 [details] [diff] [review]
[Test] hg export for checkin
[Checkin: Comment 8]


http://hg.mozilla.org/mozilla-central/rev/e6daa019b2ca
Attachment #362309 - Attachment description: [Test] hg export for checkin → [Test] hg export for checkin [Checkin: Comment 8]
Flags: in-testsuite? → in-testsuite+
Keywords: checkin-needed
Whiteboard: please check in mochitest patch
Attached patch Combined patch for branch (obsolete) — Splinter Review
Requesting approval - very minor fix to correct the existing logic. Fixes a case where "redo" in textboxes has been broken since 1999!
Attachment #362432 - Flags: approval1.9.1?
Attachment #362432 - Flags: approval1.9.1? → approval1.9.1+
Keywords: checkin-needed
Whiteboard: Please checkin branch patch to 1.9.1
Comment on attachment 364307 [details] [diff] [review]
hg export for branch checkin
[Checkin: Comment 12]


http://hg.mozilla.org/releases/mozilla-1.9.1/rev/fd629d7e3122
Attachment #364307 - Attachment description: hg export for branch checkin → hg export for branch checkin [Checkin: Comment 12]
Whiteboard: Please checkin branch patch to 1.9.1 → [fixed1.9.1b3]
The test case for this bug has a bogus </head> tag in place of </title>. See bug 546256.
You need to log in before you can comment on or make changes to this bug.