Chrome 26 beta released with improved spell checking, dev tweaks

Matthew DeCarlo

Posts: 5,271   +104
Staff

The stable version of Chrome 25 hasn't even been out for a week and Google has already promoted the next build to its beta channel and plans to roll out a completed version for Windows, Linux and Chrome OS "in the coming weeks" with Mac to follow soon after. Along with various developer-oriented tweaks (listed below), Chrome 26 brings improved spell checking with updated dictionaries and fresh support for Korean, Tamil and Albanian. Additionally, you can now sync custom dictionaries across devices.

Besides revamping the default dictionaries, Google is also adding support for grammar, homonym and context-sensitive checking -- the same technology you're likely already using in Google search and Google Docs. The engine will even correct proper nouns, such as the misspelling of Stephen Spielberg ("Steven" is correct). This feature is currently limited to English users who enable the "Ask Google for suggestions" spell check option, but Google plans to support additional languages in the near future.

Other noteworthy changes:

  • Developer preview of app launcher on Windows.
  • Forced compositing mode and threaded compositing on Mac.
  • Desktop shortcuts for multiple users (profiles) on Windows.
  • Updated UI styling of menus on Windows.
  • Asynchronous DNS resolver on Mac and Linux.
  • The template element allows you to store HTML fragments that you intend to use for any reason at any time during the lifetime of your page, but that aren’t ready or shouldn’t be used during page load.
  • CSS Transitions allow CSS property changes to occur smoothly rather than abruptly.
  • The calc() function allows you to use basic mathematical expressions anywhere a length or number is required by a CSS property.
  • The activeTab API allows your Chrome extension to interact with the currently active tab when the user invokes your extension – for example by clicking its browser action or hitting a keyboard shortcut. Since the activeTab API requires a user action to activate, it does not cause an install-time permissions warning.
  • The HTML element can be used to represent the main content of the of a document or application.
  • CSS pseudo elements (like ::before and ::after) can now be animated and transitioned.
  • Encrypted Media Extensions allow you to play protected audio and video content on the Web.
  • Enable the Experimental JavaScript flag in chrome://flags to try Object.observe(), which lets you add a listener to any JavaScript object that gets called whenever that object or its properties change.

Folks who are feeling even more adventurous may want to check out Chrome's Canary release, which contains a feature that adds a small visual indicator to tabs playing audio. More specifically, it places an animated equalizer over the site's favicon. Among other benefits, the feature would make it easy to find and close tabs with noisy ads or other annoying sounds. It's unclear if or when this feature will make it to a stable version of Chrome. Of note, Chrome Canary is mostly for developers and can be unstable.

Permalink to story.

 
I wish they would (could?) tie their web engine auto-correct to the same auto-correct in the browser. the web engine always gets it right and the browser one is no where near as good.
 
It is all garbage lol. it took a while for MS to get auto correct right in MS Office, but after a while they nailed it (IMO Office 2013 went backwards in terms of autocorrect).
 
I wish their advanced options were a little more... advanced.

Not having the ability to move the temp files directory kind of sucks for me.
 
Finally a useful update
Except for one major issue which Google still hasn't addressed in version 26: the Find command.

The Find command works on standard websites, but not on those with embedded comment boxes. To illustrate an example, here's a link to this website: Chrome App Launcher Comes To Windows. Now type the word when in the search box and the result counter on the right will display three of this search string. If you click Next, it will focus on that search string in the article. However, if you click Next, it will not move focus on the next string which is located in the comment section. It does highlight the searched string though it's a nuisance scrolling down long document to find the highlighted info I wanted. This issue doesn't affect other browsers, only Chrome. I discovered this bug in version 22 and had since submitted a bug report to Google, but so far they didn't address it in version 26 and I doubt they will in future versions.

Note that the bug I discovered in version 22 was actually my first experience with Chrome browser. It's possible this bug has existed in previous versions before I switched to Chrome.
 
Back