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

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 3.0: Easy upgrade, better performance

AngularDart 3.0 is now available. It brings better performance and smaller generated code, while also making you more productive.


Version 3.0 is an evolution: although it has some breaking changes (detailed below), it is a smooth upgrade due to minimal public API adjustments. Most of the progress is under the hood—in code quality, stability, generated code size, performance, and developer experience.

Code quality:
2731 instances of making the framework code more type safe (using sound Dart).The AngularDart framework code size is down by 12%.Many additional style updates to the codebase:Changed to use idiomatic <T> for generic methods.Removed NgZoneImpl, all the code exists in NgZone now.Stability:
Many CSS encapsulation fixes due to update with csslib package.Fixed bugs with IE11.

Performance:
For the Mail sample app, we see 30% faster time-to-interactive (currently 3812 ms on a simulated 3G connection, measured via Lighthouse).Our large app benchmark shows 2x faster render times of…

AngularDart 4

AngularDart v4 is now available. We've been busy since the release angular2 v3.1.0 in May. Not only did we "drop the 2", but we also improved the compiler and tightened up the framework to give you smaller code, we updated the package structure to improve usability, and we added several new features. Check out the updated documentation to get started.
Just angular Upgrading to v4 will require more than updating your version constraint. The package has changed names (back) to angular – dropping the 2. You'll need to update your pubspec.yaml and the corresponding imports in your code. In most instances, find-and-replace should do the trick. Going forward, the package will be called package:angular. We'll just update the version number.
Smaller code The updated compiler in 4.0 allows type-based optimizations that not only improve runtime performance but generate better code because we are able to strongly type templates. A big result of the update is that many ap…