Chrome Notoginseng Beta: Using Windows Directwrite and support <dialog> elements

Today's Chrome Beta release contains a number of new developer features. These features help you create richer, faster, and more compelling web content and applications, especially on mobile devices. Unless otherwise noted, the changes described below are valid for Android, Windows, Mac, Linux, and Chrome OS chrome.

Using the Directwrite of Windows

Chrome 37 adds support for Directwrite. This is windows for a clean, high-quality text rendering API, even for high DPI displays. Before Directwrite, Chrome uses GDI to render text. GDI dates back to the middle of the 80 's, reacting to technical compromises at that time, especially for slow-speed, low-resolution machines. Switching to Directwrite is a highly demanding user request for many years and requires the extensibility of Chrome's font rendering engine to be refactored and pipelined.

Some users should start seeing better-looking fonts and improved rendering performance. We've introduced Directwrite, but we don't need to make any changes to Web developers. Assuming everything is going well, all users will experience these improvements in the Chrome 37 stable version.

The comparison below, respectively, is not using and using the Directwrite case.

Support for new HTML elements: <dialog>

In this release, we also added support for <dialog> HTML5 elements. It enables developers to create a wide variety of dialogs in Web applications and control them through the JavaScript API. For more details, check out the some code samples and see <dialog> in action. The <dialog> element can be a good substitute for ShowModalDialog (), and, as we recently announced, ShowModalDialog () is now disabled.

some others are more New

• In Chrome 37, the Web cryptography JavaScript API is enabled by default. It allows developers to encrypt operations such as hashing, signature generation/verification, and encryption.
• Sub-pixel scaling is now supported. It makes text animations between font sizes smoother.
• Touchevents now replaces integer with a long integer, making it possible to perform high-fidelity touch operations on high-DPI displays.
• The CSS cursor value "zoom-in" and "Zoom-out" now removes the prefix.
• The number of CPU cores on the physical machine can now be obtained through navigator.hardwareconcurrency.
• The user-preferred language is now available through navigator.languages, and the Languagechange event is triggered when the language is updated.
• The CSS Shapes module allows developers to define non-rectangular parcel boundaries around floating elements.
• Npapi's deprecation work continues with a Harder-to-bypass blocking UI, as we announced earlier.
• The default equal-width font on Windows uses Consolas instead of courier New.

As always, visit chromestatus.com/features to get a complete overview of the features of the chrome developer and focus on +google chrome developers for more timely updates.

Posted by Emil A Eklund, software Engineer and Senior Blog directwriter

Disclaimer: This article is from http://blog.chromium.org, the English version of the original link for http://blog.chromium.org/2014/07/chrome-37-beta-directwrite-on-windows.html. For the purpose of sharing information, KINGYSU has translated the English version.

Reproduced from the nest rain