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.

Comments

Popular posts from this blog

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" misc@dartlang.org post originally written by Bob Nystrom. It is being posted here as the explanations still ring true.)

Bob writes:


"static", "final", and "const" mean entirely distinct things in Dart:

"static" means a member is available on the class itself instead of on instances of the class. That's all it means, and it isn't used for anything else. static modifies *members*.

"final" means single-assignment: a final variable or field *must* have an initializer. Once assigned a value, a final variable's value cannot be changed. final modifies *variables*.

"const" has a meaning that's a bit more complex and subtle in Dart. const modifies *values*. You can use it when creating collections, like const [1, 2, 3], and when constructing objects (instead of new) like const Point(2, 3). Here, const means that the object's entire deep state can be determ…

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…

Dart 1.12 Released, with Null-Aware Operators and more

Dart 1.12.0 is now released! It contains the new null-aware operators language feature, and enhancements to pub, Observatory, dartdoc, and much more.

Null-aware operators

The new null-aware operators help you reduce the amount of code required to work with references that are potentially null. This feature is a collection of syntactic sugar for traversing (potentially null) object calls, conditionally setting a variable, and evaluating two (potentially null) expressions.

Click or tap the red Run button below to see them in action.

??

  if null operator. `expr1 ?? expr2` evaluates to `expr1` if not `null`, otherwise `expr2`.


??=

  null-aware assignment. `v ??= expr` causes `v` to be assigned `expr` only if `v` is `null`.

x?.p

  null-aware access. `x?.p` evaluates to `x.p` if `x` is not `null`, otherwise evaluates to `null`.

x?.m()

  null-aware method invocation. `x?.m()` invokes `m` only if `x` is not `null`.

Learn more about Dart's null-aware operators in our Language Tour.

.packages fi…