Add CHANGELOG entries for Dartium and dart:html changes

CHANGELOG.md

 ## 1.14.0
 
 ### Core library changes
 * `dart:math`
   * `Random` added a `secure` constructor returning a cryptographically secure
     random generator which reads from the entropy source provided by the
     embedder for every generated random value.
 
 ## 1.13.0
 
@@ skipping 14 matching lines @@
 
 * `dart:core`
   * `Uri` added `removeFragment` method.
   * `String.allMatches` (implementing `Pattern.allMatches`) is now lazy,
     as all `allMatches` implementations are intended to be.
   * `Resource` is deprecated, and will be removed in a future release.
 
 * `dart:developer`
   * Added `Timeline` class for interacting with Observatory's timeline feature.
   * Added `ServiceExtensionHandler`, `ServiceExtensionResponse`, and `registerExtension` which enable developers to provide their own VM service protocol extensions.
-  
+
+* `dart:html`
+  * The return type of some APIs changed from `double` to `num`. Dartium is now
+    using
+    JS interop for most operations. JS does not distinguish between numeric

[kevmoo, 2015/11/11 22:00:49]

Folks should only see issues when running in checked-mode, right? Might want to
mention that...

[Alan Knight, 2015/11/11 23:00:12]

Hmm. I was thinking it was more than that, but I'm not seeing any operations on
double that aren't on int. The reverse case has several, but it looks like,
other than checking runtimeType or similar, it might just be checked mode. Added
a sentence about it.

+    types, and will return a number as an int if it fits in an int. You may
+    need to insert a `toDouble()` call or accept `num`. Examples of APIs that
+    are affected include `Element.getBoundingClientRect` and
+    `TextMetrics.width`.
+
 * `dart:io`
   * **Breaking:** Secure networking has changed, replacing the NSS library
     with the BoringSSL library. `SecureSocket`, `SecureServerSocket`,
     `RawSecureSocket`,`RawSecureServerSocket`, `HttpClient`, and `HttpServer`
     now all use a `SecurityContext` object which contains the certificates
     and keys used for secure TLS (SSL) networking.
 
     This is a breaking change for server applications and for some client
     applications. Certificates and keys are loaded into the `SecurityContext`
     from PEM files, instead of from an NSS certificate database. Information
     about how to change applications that use secure networking is at
     https://www.dartlang.org/server/tls-ssl.html
 
   * `HttpClient` no longer sends URI fragments in the request. This is not
     allowed by the HTTP protocol.
     The `HttpServer` still gracefully receives fragments, but discards them
     before delivering the request.
   * To allow connections to be accepted on the same port across different
     isolates, set the `shared` argument to `true` when creating server socket
     and `HttpServer` instances.
     * The deprecated `ServerSocketReference` and `RawServerSocketReference`
       classes have been removed.
     * The corresponding `reference` properties on `ServerSocket` and
       `RawServerSocket` have been removed.
 
+* `dart:indexed_db`

[kevmoo, 2015/11/11 22:00:49]

Roll all of these under `dart:html` – a comma-separated list is fine

[Alan Knight, 2015/11/11 23:00:12]

Done.

+  * APIs returning double have changed to num. See `dart:html` discussion.
+
 * `dart:isolate`
   * `spawnUri` added an `environment` named argument.
 
+* `dart:svg`
+  * APIs returning double have changed to num. See `dart:html` discussion.
+
+* `dart:web_audio`
+  * APIs returning double have changed to num. See `dart:html` discussion.
+
+* `dart:web_gl`
+  * APIs returning double have changed to num. See `dart:html` discussion.
+
+* `dart:web_sql`
+  * APIs returning double have changed to num. See `dart:html` discussion.
+
 ### Tool changes
 
 * `docgen` and 'dartdocgen' no longer ship in the sdk. The `docgen` sources have
    been removed from the repository.
 
 * This is the last release to ship the VM's "legacy debug protocol".
   We intend to remove the legacy debug protocol in Dart VM 1.14.
 
 * The VM's Service Protocol has been updated to version 3.0 to take care
   of a number of issues uncovered by the first few non-observatory
   clients.  This is a potentially breaking change for clients.
 
+* Dartium has been substantially changed. Rather than using C++ calls into
+  Chromium internals for DOM operations it now uses JS interop.
+  The DOM objects in `dart:html` and related libraries now wrap
+  a JavaScript object and delegate operations to it. This should be
+  mostly transparent to users. However, performance and memory characteristics
+  may be different from previous versions. There may be some changes in which

[kevmoo, 2015/11/11 22:00:49]

What does it mean to be "wrapped as Dart objects"? How does it affect how I
code?

[Alan Knight, 2015/11/11 23:00:12]

Clarified.

+  DOM objects are wrapped as Dart objects, e.g. Window objects are always
+  returned as Dart, even when used cross-frame. We expect the change to using
+  JS interop will make it much simpler to update to new Chrome versions.
+
 ## 1.12.2 - 2015-10-21
 
 ### Core library changes
 
 * `dart:io`
 
   * A memory leak in creation of Process objects is fixed.
 
 ## 1.12.1 - 2015-09-08
 
@@ skipping 536 matching lines @@
     they will keep the Dart process alive until they time out. This fixes the
     handling of persistent connections. Previously, the client would shut down
     immediately after a request.
 
   * **Breaking change:** `HttpServer` no longer compresses all traffic by
     default. The new `autoCompress` property can be set to `true` to re-enable
     compression.
 
 * `dart:isolate`: `Isolate.spawnUri` added the optional `packageRoot` argument,
   which controls how it resolves `package:` URIs.