Yesterday Chrome 33 for Windows, OSX and Linux was released by Google Chrome team. Today we deployed Chrome 33 to all our systems and it's now available to all our users.

Cross-browser testing in Chrome 33

Try Chrome 33 in Browserling now!

Chrome 33 implements the following new features and updates:

  • CSS font-kerning - A CSS property to control text kerning.
  • Custom Elements - Method for registering (creating) custom elements in script.
  • Opus in MSE and <video> - Ability to play the open source WebRTC preferred audio codec - Opus in MSE and &ltvideo> tags on the for the webM and matroska containers. Please note that we have had Opus support in chromium since M25. This change enables Opus playback on MSE and <video> tags.
  • Page Visibility API - Provides an API to ask whether the current tab is visible or not. If you, you might want to throttle back action or set an idle state.
  • VTTCue - The VTTCue interface, part of WebVTT. Previously the members of VTTCue were on the TextTrackCue interface and there was a TextTrackCue constructor, now the VTTCue constructor must be used instead.
  • Web Speech API (synthesis) - Enables web developers to incorporate speech synthesis into their web pages. Uses whatever the platform provides for synthesis.
  • requestAutocomplete() - Allows a form to be filled out on demand by the browser's autofill. Particularly for mobile applications, this solves the problem of working with long or even multi-page forms. For merchants, this results in improved conversion rates, sorely needed in mobile purchase scenarios.

Significant changes in Android version of Chrome 33:

  • Download progress notification for file downloads using the Chrome network stack.
  • Updated help and feedback UI.
  • Support for <datalist> tag.

Significant changes in iOS version of Chrome 33:

  • Stability and security updates.

The new release also includes 28 security fixes. Chrome team highlighted the following fixes that were contributed by external researchers and were particularly interesting:

  • CVE-2013-6652: Issue with relative paths in Windows sandbox named pipe policy. Credit to tyranid.
  • CVE-2013-6653: Use-after-free related to web contents. Credit to Khalil Zhani.
  • CVE-2013-6654: Bad cast in SVG. Credit to TheShow3511.
  • CVE-2013-6655: Use-after-free in layout. Credit to cloudfuzzer.
  • CVE-2013-6656: Information leak in XSS auditor. Credit to NeexEmil.
  • CVE-2013-6657: Information leak in XSS auditor. Credit to NeexEmil.
  • CVE-2013-6658: Use-after-free in layout. Credit to cloudfuzzer.
  • CVE-2013-6659: Issue with certificates validation in TLS handshake. Credit to Antoine Delignat-Lavaud and Karthikeyan Bhargavan from Prosecco, Inria Paris.
  • CVE-2013-6660: Information leak in drag and drop. Credit to bishopjeffreys.
  • CVE-2013-6661: Various fixes from internal audits, fuzzing and other initiatives. Of these, seven are fixes for issues that could have allowed for sandbox escapes from compromised renderers.

Happy cross-browser testing in Chrome 33!