7 replies to this topic

[zenpop]

Just did the latest upgrade for OSX Leopard (10.3.4), hoping the Firefox situation had been fixed. It hasn't.

Downloaded Chrome, by Google, and it ALSO doesn't work with SC.

Don't like using Safari. I'd assumed by now the Firefox problem would have been corrected (by Firefox?) What's up with that?

What's the word? I can't be the only person with this issue.


zp

[Evan Gross]

zenpop, on Jan 25 2010, 04:01 PM, said:

Just did the latest upgrade for OSX Leopard (10.3.4), hoping the Firefox situation had been fixed. It hasn't.

Downloaded Chrome, by Google, and it ALSO doesn't work with SC.

Don't like using Safari. I'd assumed by now the Firefox problem would have been corrected (by Firefox?) What's up with that?

What's the word? I can't be the only person with this issue.


zp

Like I said, this can't be fixed on Spell Catcher’s side. So a new version of Spell Catcher can't make any difference.

Please send your feedback to the Mozilla and Google folks. I haven't played with Chrome, but I guess it's time to take a look and see what they're doing wrong…

[jeffcovey]

I'm testing SC prior to purchase, and also finding it unusable with Chrome (for example, if I type "abuut" and chose "about" from the spelling corrections menu, it replaces it with "aout"). Is there any news on this? I tried configuring it like Outlook as suggested in another discussion, but it didn't help.

Thanks,
Jeff

[Evan Gross]

jeffcovey, on 13 February 2011 - 04:11 PM, said:

I'm testing SC prior to purchase, and also finding it unusable with Chrome (for example, if I type "abuut" and chose "about" from the spelling corrections menu, it replaces it with "aout"). Is there any news on this? I tried configuring it like Outlook as suggested in another discussion, but it didn't help.

Thanks,
Jeff

Yeah, Chrome is just a really bad Mac OS X "citizen", not playing by the rules for dealing with text input. Spell Catcher tries to work around Chrome's poor (incorrect) implementation, but the only real solution is for Chrome to be fixed. Too bad, older versions of Chrome worked fine…

As for Outlook, double-check your settings, make sure that Spell Catcher's input method component IS being used whenever Outlook is active (i.e. you see the yellow checkmark without the "64' badge in Outlook).

[jeffcovey]

I don't use Outlook, I said I was configuring SC to interact with Chrome as in your suggestions for Outlook, as discussed here. It hasn't helped. I'm sorry there's not a current workaround for this, I'm going back to Firefox for the moment, but prefer Chrome.

Thanks for your help,
Jeff

[Evan Gross]

jeffcovey, on 14 February 2011 - 11:44 AM, said:

I don't use Outlook, I said I was configuring SC to interact with Chrome as in your suggestions for Outlook, as discussed here. It hasn't helped. I'm sorry there's not a current workaround for this, I'm going back to Firefox for the moment, but prefer Chrome.

Thanks for your help,
Jeff

No, that won't help - Chrome is just "too far gone".

You're best off with a real Mac OS X web browser - Safari or OmniWeb. Cross-platform browsers never have proper text input implementations.

[jeffcovey]

Unfortunately, I've seen too many websites mysteriously fail to work with Safari, including, ironically, store.apple.com. I tried to buy an iPod Touch there, and Safari wouldn't submit my order. I switched to Firefox, and it went through fine. I'd like to use Safari, but it's just failed too many times for me.

Thanks,
Jeff

[Evan Gross]

jeffcovey, on 22 February 2011 - 01:39 PM, said:

Unfortunately, I've seen too many websites mysteriously fail to work with Safari, including, ironically, store.apple.com. I tried to buy an iPod Touch there, and Safari wouldn't submit my order. I switched to Firefox, and it went through fine. I'd like to use Safari, but it's just failed too many times for me.

Thanks,
Jeff

Strange - never seen it fail on me, ever...