"Is tehre a solution to tehre problem for when tehre traveling?"
I've compared Chrome 25 and Chrome 26. The difference is striking: Chrome 25 shows the same suggestions for the 3 spelling errors ("there", "ether", "three", "Tehran"), while Chrome 26 shows different suggestions for each mistake.
Here's the contextual menu from Chrome 25:

... and here are the suggestions from Chrome 26:



The most interesting thing is that Chrome shows the same suggestions even if you disable "ask Google for suggestions", so they're generated locally (only the errors with a green underline are detected by the web service). Obviously, the web service is useful in other cases, but it's surprising to see that Chrome's context-sensitive spell checking works offline, even if only in a limited way.
No comments:
Post a Comment