[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





--- Comment #6 from Hironori Bono <hbono at chromium.org>  2012-04-12 01:10:13 PST ---
Greetings Niwa-san,

Thanks for your response.
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?

Regards,

Hironori Bono

(In reply to comment #5)
> Can we tie this fix to the usage of TextCheckingClient::requestCheckingOfString instead of adding new flag?  It's non-obvious that we should be calling this function with a flag when some other port start using this API.

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