Bug 18835

Summary: spelling underlines disappear when they shouldn't
Product: WebKit Reporter: Eric Seidel (no email) <eric>
Component: New BugsAssignee: Hironori Bono <hbono>
Status: RESOLVED FIXED    
Severity: Normal CC: justin.garcia
Priority: P2    
Version: 525.x (Safari 3.1)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
A Quick Fix justin.garcia: review+

Eric Seidel (no email)
Reported 2008-05-01 14:08:03 PDT
This isn't 100% reproducible, but I can usually get it to happen with the following steps: 1. click into a textarea (add comment field on this page), or editable html region (gmail) 2. type the following: The quick brown foxxx jumped over 3. hit the back arrow four times to move the cursor to the beginning of 'over' 4. hit return The red squiggle under foxxx will disappear. I haven't tried on mac, just windows.
Attachments
A Quick Fix (3.54 KB, patch)
2009-01-08 00:04 PST, Hironori Bono
justin.garcia: review+
Hironori Bono
Comment 1 2009-01-08 00:04:12 PST
Created attachment 26522 [details] A Quick Fix I accidentally noticed a cause of this bug while investigating another issue. Somehow the InsertLineBreakCommand::doApply() function forgot copying markers while splitting a text node with a line-break key even though there is a CompositeEditCommand::splitTextNode() function, which splits a text node and copy markers. I'm not sure it is correct to call the CompositeEditCommand::splitTextNode() function here, though.
Justin Garcia
Comment 2 2009-01-08 00:50:28 PST
Comment on attachment 26522 [details] A Quick Fix so, deleteTextFromNode removes spelling markers from text even if the deletion doesn't effect them? we should document that problem. do we need to make this change to InsertParagraphSeparatorCommand and BreakBlockquoteCommand? r=me
Justin Garcia
Comment 3 2009-01-08 00:55:48 PST
> so, deleteTextFromNode removes spelling markers from text even if the deletion > doesn't effect them? we should document that problem. Oops my mistake, I misread the code, I thought it deleted what was after the caret, not what was before. Disregard that bit.
Hironori Bono
Comment 4 2009-01-08 20:28:32 PST
Thank you for your review and comments. > do we need to make this change to InsertParagraphSeparatorCommand and > BreakBlockquoteCommand? As far as I read the InsertParagraphSeparatorCommand::doApply() and BreakBlockquoteCommand::doApply() functions, they already use the splitTextNode() function to split a text node. (This is a reason why my quick fix uses the splitTextNode() function.) Regards, Hironori Bono
Darin Fisher (:fishd, Google)
Comment 5 2009-01-28 11:38:37 PST
Darin Fisher (:fishd, Google)
Comment 6 2009-01-28 16:51:02 PST
Added missing layout test results: http://trac.webkit.org/changeset/40341
Note You need to log in before you can comment on or make changes to this bug.