Dartium support for Uri.base (dart-side)

tools/dom/src/native_DOMImplementation.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 part of html;
 
 class _ConsoleVariables {
   Map<String, Object> _data = new Map<String, Object>();
 
   /**
@@ skipping 517 matching lines @@
 }
 
 final _printClosure = window.console.log;
 final _pureIsolatePrintClosure = (s) {
   throw new UnimplementedError("Printing from a background isolate "
                                "is not supported in the browser");
 };
 
 final _forwardingPrintClosure = _Utils.forwardingPrint;
 
+final _uriBaseClosure = () => Uri.parse(window.location.href);
+
+final _pureIsolateUriBaseClosure = () {
+  throw new UnimplementedError("Uri.base on a background isolate "
+                               "is not supported in the browser");

[siva, 2013/10/28 18:44:51]

Shouldn't we have some kind of base for this too maybe based on the URI
specified in spawnUri ?

[vsm, 2013/10/29 14:10:53]

Any idea how I can get this base for a background isolate?  Who sets it?

On 2013/10/28 18:44:51, siva wrote:

[floitsch, 2013/10/29 18:05:21]

The spawnUri already comes with an initial message. We can easily extend it to
also receive a base-URI.
So, if you we agree on what should be there we can set it during the spawnUri
start-up.

+};
+
  class _Timer implements Timer {
   var _canceler;
 
   _Timer(int milliSeconds, void callback(Timer timer), bool repeating) {
 
     if (repeating) {
       int id = window._setInterval(() {
         callback(this);
       }, milliSeconds);
       _canceler = () => window._clearInterval(id);
@@ skipping 66 matching lines @@
   _scheduleImmediateHelper._schedule(callback);
 };
 
 get _pureIsolateScheduleImmediateClosure => ((void callback()) =>
   throw new UnimplementedError("scheduleMicrotask in background isolates "
                                "are not supported in the browser"));
 
 void _initializeCustomElement(Element e) {
   _Utils.initializeCustomElement(e);
 }