Skip to main content

Deprecation notice: Migrate from dart:dom to dart:html

Posted by Vijay Menon


We strive to improve the web development experience, and we’ve been working hard on a better DOM interface for browser programming. The Dart team has been developing the dart:html library and improving its performance for the past several months, and we believe that it provides a much better experience for Dart programmers than the old dart:dom library.

For example, dart:html handles cross-browser compatibility for various cases (with more compat work coming), provides a more jQuery like experience for querying the DOM, and makes interaction with the DOM feel natural to Dart developers.

We are now ready to deprecate dart:dom in favor of dart:html (tracked via Bug 2517).  This means that we will remove the dart:dom library from user facing code no sooner than Monday, May 7th. Please migrate your code to dart:html before this date, and report any problems at http://dartbug.com. Sometime soon after this date, you will not be able to access dart:dom.

The dart:html library attempts to clean up traditional DOM programming, but it also provides an “escape hatch” if you really need to drop to the traditional DOM API. Whenever the dart:html has removed or significantly changed a DOM API, it provides a legacy escape hatch of the form “$dom_OLD_API”. We don’t recommend using these methods unless you have a very good reason to, such as porting legacy code to Dart.

We suspect that most developers are already using dart:html, but if you aren’t please see Bob Nystrom’s article on Improving the DOM and the API docs for dart:html. As always, your feedback is very important. Please join the discussion in the Dart mailing list and let us know how your upgrade to dart:html went.

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and – even more so – from large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …