3 replies to this topic

[Mike Ihnat]

Hello!

I finally changed from Chrome to Safari and to my chagrin that evil empire Google threw another wrench in the works with using SCX and Google docs. What happens is that the abbreviation expands but leaves the leaves the abbreviation behind.

Examples are: thatsthat’s, dontdon’t, isntisn’t, etc. etc.

Can anyone tell me how I might overcome this or has the Empire struck back again?

Thanks much!!

Mike

[Evan Gross]

Mike Ihnat, on 21 March 2011 - 11:56 AM, said:

Hello!

I finally changed from Chrome to Safari and to my chagrin that evil empire Google threw another wrench in the works with using SCX and Google docs. What happens is that the abbreviation expands but leaves the leaves the abbreviation behind.

Examples are: thatsthat’s, dontdon’t, isntisn’t, etc. etc.

Can anyone tell me how I might overcome this or has the Empire struck back again?

Thanks much!!

Mike

What version of Mac OS X?
What version of Safari?
What version of Spell Catcher X?

EXACT same behavior in both Safari and Firefox?

[Mike Ihnat]

I just updated FF to 4.0 beta 8 (from 4.0 beta 2) and the issue seemed to resolve but yes, up until then it was the same. Ugh!

Safari is still a problem as is 5.0.4
SC 10.3.7
OS 10.6.6.

Thanks much!!

Mike

[Evan Gross]

Mike Ihnat, on 22 March 2011 - 03:23 PM, said:

I just updated FF to 4.0 beta 8 (from 4.0 beta 2) and the issue seemed to resolve but yes, up until then it was the same. Ugh!

Safari is still a problem as is 5.0.4
SC 10.3.7
OS 10.6.6.

Thanks much!!

Mike

Yeah, I can reproduce this. However, I have no idea what's going on (internally) with the text editing view/widget that Google Docs is using. They must be overriding most or all of Safari/WebKit's text editing functionality, as Safari definitely (normally) supports all the APIs/features that Spell Catcher uses to insert text.

No idea at this time just how to work-around it - Google seems to insist on doing their own thing and circumventing or just not using the capabilities that are available to it. That would be fine if they would properly implement the text input features that are required, but they simply don't (or perhaps won't).

I'll try to figure out what's going on in the next few days - no promises, really. I need to do some testing with Apple's own input methods to see if they're broken as well...