[Webkit-unassigned] [Bug 83748] [Chromium] Remove existing markers when updating markers.

[bugzilla-daemon at webkit.org]

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


Ryosuke Niwa <rniwa at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jpu at apple.com




--- Comment #7 from Ryosuke Niwa <rniwa at webkit.org>  2012-04-12 01:42:06 PST ---
(In reply to comment #6)
> Even though this is just a random thought, one option is splitting didCheck into two functions: didCheckSucceeded() and didCheckFailed(). In the current usage of Chrome, Chrome calls this function for a couple of purposes: notifying Chrome finishes the given text-check request successfully and notifying Chrome has an error while processing the request. Chrome needs to erase existing markers only when it finishes checking text successfully. On the other hand, Chrome should not erase existing markers when it fails checking the text. Would it be possible to give me your thoughts about this idea?

That makes sense to me at least. Maybe jpu and morrita have some opinions here?

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