[Webkit-unassigned] [Bug 37050] New: Toggle spell check doesn't update markers

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 2 16:10:12 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=37050

           Summary: Toggle spell check doesn't update markers
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
               URL: https://bugs.webkit.org/enter_bug.cgi?product=WebKit
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Minor
          Priority: P2
         Component: HTML Editing
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tonyg at chromium.org
                CC: ojan at chromium.org


To reproduce:
1. Open any page with a textarea, for instance
https://bugs.webkit.org/enter_bug.cgi?product=WebKit
2. Enter misspelled text, for instance "asdf asdf"
3. Right click on the text area and turn spell checking off. Notice spell
markers.
4. Right click on the text area and turn spell checking back on. Notice spell
markers.

Expected:
After disabling all markers should be removed. After enabling all markers
should return.

Actual:
In Safari, markers are removed after disabling, but they do not return after
enabling.
In Chrome, markers are only removed after disabling and selecting the text area
again. Like Safari, they do not return after enabling.

The only way to recheck appears to be to go through and click on each word to
check it.

I propose that in Editor.cpp:toggleContinuousSpellChecking(), the markers
should be updated after toggling. I'm interested in putting a patch together
which does this and adds a LayoutTest that ensures markers are updated after
toggling on and off.

This is a step towards fixing the more significant issue that markers are not
updated when the language is changed in Chrome (http://crbug.com/21225). After
this fix is in, I am planning to just toggle between language switches.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list