Chrome 98 arrived a few months ago, and since it was announced that the Stable release channel was changed to a four-week release cycle this past week, it’s time to wait for Chrome 99 to ship

Share on facebook
Share on twitter
Share on linkedin
Share on pinterest
Share on whatsapp

If you buy something from a this link, myelectricsparks Media may earn a commission. See our Read More.

Chrome 99 will be available on July 1 with enhanced PWAs and a heatedly debated JS specification change.

There are not a lot of brand new features included in this release which is understandable since Google is getting close to reaching the Chrome 100 milestone.

In the beginning, Chrome 99 will alter how the JavaScript (JS) StyleSheets standard has been adopted. It previously utilized the FrozenArray backing array but now relies on ObservableArray. In addition, the new techniques will allow for the more accessible altering of JS arrays. Although this is quite technical, the fascinating aspect to our readers is the changes in these specifications have already been discussed by Microsoft, Mozilla, Apple, and Google since the beginning of 2018.

At the moment, Google will incorporate this feature as part of Chrome 99. Both Mozilla as well as Microsoft, approves the change. However, we have Apple’s WebKit team, which has decided not to accept the new implementation, stating that there is no benefit worth the difference. Google has said that it will continue to provide that it is backward compatible with the previous performance but has stated in a somewhat disappointed tone that:

WebKit is still doubtful of the usefulness of this feature despite the consensus shared by the community of web components and the backing of the developer’s community. The risk for interop is that WebKit decides not to adopt this new feature. Chances of compatibility (from the switch of FrozenArray into ObservableArray) are likely to be low since the same re-assignment semantics continue to be used. As documentation gets better and the use of the system grows, We expect re-assignments to decrease and the possibility of change (e.g., adoptedStyleSheets.push()) to expand.

The most recent version of¬†Chrome comes with an updated Handwriting Recognition API¬†that web developers can use to provide capabilities for inking, for example, using it in a note-taking website application. It’s not necessary to rely on third-party interfaces.

Regarding web applications, Chrome 99 will allow installed Progressive Web Apps (PWAs) to fill larger areas on the screen to look like native apps rather than web-based apps.

Chrome 99 will be available on July 1 with enhanced PWAs and a heatedly debated JS specification change.

On the CSS aspect on the CSS side, the¬†calculation() mathematical function is now working more closely with the specifications of the CSS community.¬†Cascade Layers in CSS¬†can make the management of layers in web components more straightforward for developers. Additionally, a change to the¬†“-WebKit-standard” font-family property has been removed¬†to make it easier to compatible with Firefox developers. Developers can make use of “-WebKit-body” specifically instead. If you’re doing textual formatting with CSS,¬†check out the new properties available in Chrome 99 on this page.

Canvas 2D API¬†is being upgraded¬†to achieve features at the same level as other 2D APIs, take advantage of the existing CSS features, and increase performance. The API is mainly used in games and “full full-featured applications.” In the same way, Gamepad API is being developed.¬†Gamepad API is currently being upgraded to conform to the standard specifications.

Google also offers an updated interface for users of the File System Access API, which provides fast and in-place access to files when you’re an application developer who uses Origin Private File System. Origin Private File System. The implementation is handled through Apple’s WebKit team, too.

There are plenty of additional features for developers, including Autofill in ShadowDOM and a programmatic picking tool to select HTML input components, the introduction of Intl Enumeration and Intl Locale Info APIs as well as a brand-new destination for PaintWorklet. There’s more, as there are many new features included in Chrome 99 DevTools. You¬†can also find the complete list here.

Chrome 99 will begin roll-out in the late hours of the day. If it fails to update automatically to version 99 for you over the day, go to the help > more about Google Chrome to trigger the update as soon as it is available. The next update will be Chrome 100, which will hit the Beta channel on March 3 and arrive in Stable on March 29.

Chrome 99 will be available on July 1 with enhanced PWAs and a heatedly debated JS specification change.