4 replies to this topic

[MRubenzahl]

I have had the following issue for a long, long time and scanning the board here it sounds like maybe some people are successfully using SC and Chrome??

For me, SC used with Google Chrome does an extra backspace, so:

my ppl

expands to

mypeople

rather than to

my people

It's 100% consistent. Happens whether I use the InputMethod or the Input Component. Happens whether or not I check "Make replacements directly without backspacing where possible."

Mac OS X 10.6.8, SC 10.4, Google Chrome latest (and the problem has been over a year, with prior SC and Chrome versions, as well).

[Evan Gross]

MRubenzahl, on 03 October 2011 - 08:14 PM, said:

I have had the following issue for a long, long time and scanning the board here it sounds like maybe some people are successfully using SC and Chrome??

For me, SC used with Google Chrome does an extra backspace, so:

my ppl

expands to

mypeople

rather than to

my people

It's 100% consistent. Happens whether I use the InputMethod or the Input Component. Happens whether or not I check "Make replacements directly without backspacing where possible."

Mac OS X 10.6.8, SC 10.4, Google Chrome latest (and the problem has been over a year, with prior SC and Chrome versions, as well).

I was pretty sure that Spell Catcher X 10.4 was generally OK with Chrome, but I had an older version installed (8). So I downloaded the latest stable release (14) and fired it up. I did initially see a couple of strange things happening, but after a bit more playing and trying to figure out what as going on, strangely things did start to work as expected (correctly - or at least as well as could be expected with such an evil application). At least for a short time, I did observe the behavior you describe, though not exactly the same. I have no idea what I might have done to get things working (as I remember they used to with Chrome 8).

Anyway, I'll keep on eye on it (periodically) and hopefully be able to reproduce this problem. All I can recommend is that you play around and see if you can get the (correct results) that I did.

I know others have had luck, and that Spell Catcher X 10.4 has some tweaks in its input methods specifically for Chrome. I can verify that there are issues with the input method component, but the input method application (64-bit) seemed to be fine.

Let me know if you see any changes…

[MRubenzahl]

Interesting. For me it does the behavior 100% of the time.

[zsoltmag]

I probably have the same issue. For a while I tried to ignore it, but now it is starting to be kind of annoying. I use Chrome 15, and SC 10.4. I do have interactive spell checking switched on with suggest spelling window option.
When it encounters a misspelled word, the windows opens and offers the suggestion with command+number list, when I hit one of the command+number combinations, it does not replace the misspelled word with the selected one, but it adds the word to the end of the sentence.
Is this a known issue? I think this started after I upgraded to Lion. I'm not sure if it happens in safari, I just tried it with text edit and there it works fine.
Thanks for help,
Zsolt

[Evan Gross]

zsoltmag, on 15 November 2011 - 02:20 AM, said:

I probably have the same issue. For a while I tried to ignore it, but now it is starting to be kind of annoying. I use Chrome 15, and SC 10.4. I do have interactive spell checking switched on with suggest spelling window option.
When it encounters a misspelled word, the windows opens and offers the suggestion with command+number list, when I hit one of the command+number combinations, it does not replace the misspelled word with the selected one, but it adds the word to the end of the sentence.
Is this a known issue? I think this started after I upgraded to Lion. I'm not sure if it happens in safari, I just tried it with text edit and there it works fine.
Thanks for help,
Zsolt

It's a Chrome "thing". As stated in this thread, Chrome is a really nasty Mac OS X test input client, and I can only do so much on my end to work around the (fundamental) problems it has. Spell Catcher X 10.4.1 should improve things somewhat, but the reality is that Google is the only one that can make their product compatible with input methods.

If you send an email to our feedback address (Spell Catcher app, Help > Send Feedback by E-Mail) telling me who you are and what you're after, I can send you an Input Method Tuner file that should make things work better for you. Disclaimer: the next time Google updates Chrome, the workarounds in this Tuner may well break. I know earlier versions of Chrome worked worse with the current Tuner, the same may be the case with any Chrome updates.