Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(28)

Issue 928473002: [mac] Init spellcheck service. (Closed)

Created:
5 years, 10 months ago by please use gerrit instead
Modified:
5 years, 10 months ago
Reviewers:
groby-ooo-7-16
CC:
chromium-reviews, groby+spellwatch_chromium.org, rlp+watch_chromium.org, rouslan+spellwatch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

[mac] Init spellcheck service. BUG=454992 Committed: https://crrev.com/4ca14cb4922b883fde5419b9b176ef58b5296bf2 Cr-Commit-Position: refs/heads/master@{#317179}

Patch Set 1 : #

Patch Set 2 : Move service init to UI thread. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+7 lines, -0 lines) Patch
M chrome/browser/spellchecker/spellcheck_message_filter_mac.cc View 1 1 chunk +7 lines, -0 lines 0 comments Download

Messages

Total messages: 25 (9 generated)
please use gerrit instead
This is not the final patch, but it fixes spellcheck on Mac already. I just ...
5 years, 10 months ago (2015-02-13 16:42:59 UTC) #2
please use gerrit instead
Rachel, ptal. In an ideal world, I would probably rearchitect many things in spellcheck. But ...
5 years, 10 months ago (2015-02-13 23:34:05 UTC) #5
groby-ooo-7-16
Where does Views instantiate the factory? Think you can find a way to guarantee a ...
5 years, 10 months ago (2015-02-18 17:51:55 UTC) #6
please use gerrit instead
Views initializes spellcheck service in the following locations, which are not used on Mac. SpellCheckMessageFilter::OnSpellCheckerRequestDictionary ...
5 years, 10 months ago (2015-02-18 20:30:55 UTC) #7
groby-ooo-7-16
Alright, alright... LGTM
5 years, 10 months ago (2015-02-19 00:21:00 UTC) #8
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/928473002/40001
5 years, 10 months ago (2015-02-19 00:28:22 UTC) #10
commit-bot: I haz the power
Try jobs failed on following builders: mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/35714)
5 years, 10 months ago (2015-02-19 01:50:32 UTC) #12
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/928473002/40001
5 years, 10 months ago (2015-02-19 02:40:30 UTC) #14
commit-bot: I haz the power
Try jobs failed on following builders: mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/35779)
5 years, 10 months ago (2015-02-19 03:54:39 UTC) #16
please use gerrit instead
Failure is reliable. Looking into it.
5 years, 10 months ago (2015-02-19 15:31:12 UTC) #17
please use gerrit instead
Moved service initialization from constructor to SpellCheckMessageFilterMac::OnRequestTextCheck, because it needs to happen on the UI ...
5 years, 10 months ago (2015-02-19 23:10:32 UTC) #19
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/928473002/60001
5 years, 10 months ago (2015-02-19 23:23:37 UTC) #21
groby-ooo-7-16
I'm not happy with doing that in RequestTextCheck - that's a cost for every check ...
5 years, 10 months ago (2015-02-19 23:41:15 UTC) #22
commit-bot: I haz the power
Committed patchset #2 (id:60001)
5 years, 10 months ago (2015-02-20 00:07:31 UTC) #23
commit-bot: I haz the power
Patchset 2 (id:??) landed as https://crrev.com/4ca14cb4922b883fde5419b9b176ef58b5296bf2 Cr-Commit-Position: refs/heads/master@{#317179}
5 years, 10 months ago (2015-02-20 00:07:59 UTC) #24
please use gerrit instead
5 years, 10 months ago (2015-02-20 15:22:21 UTC) #25
Message was sent while issue was closed.
On 2015/02/19 23:41:15, groby wrote:
> I'm not happy with doing that in RequestTextCheck - that's a cost for every
> check we do request. Grumble. _Especially_ since you only do this to satisfy a
> unit test which doesn't _have_ a UI thread. 
> 
> The proper fix would be to send an init message from cocoa_spelling_engine,
just
> like we do for hunspell_engine. (Except that's yet one more path that's
> different for Cocoa. So, no)
> 
> Sigh.

Let me know if you'd like me to revert and look for a better solution.

Powered by Google App Engine
This is Rietveld 408576698