Fix client/html_tests so they use the new framework.

client/html/src/DocumentFragmentWrappingImplementation.dart

 // Copyright (c) 2011, 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.
 
 class FilteredElementList implements ElementList {
   final Node _node;
   final NodeList _childNodes;
 
   FilteredElementList(Node node): _childNodes = node.nodes, _node = node;
 
@@ skipping 89 matching lines @@
   List<Element> getRange(int start, int length) =>
     _filtered.getRange(start, length);
   int indexOf(Element element, int startIndex) =>
     _filtered.indexOf(element, startIndex);
   int lastIndexOf(Element element, int startIndex) =>
     _filtered.lastIndexOf(element, startIndex);
   Element last() => _filtered.last();
 }
 
 class EmptyStyleDeclaration extends CSSStyleDeclarationWrappingImplementation {
-  String get cssText() => "";
-  int get length() => 0;
-  CSSRule get parentRule() => null;
-  CSSValue getPropertyCSSValue(String propertyName) => null;
-  String getPropertyPriority(String propertyName) => "";
-  String getPropertyShorthand(String propertyName) => null;
-  String getPropertyValue(String propertyName) => null;
-  bool isPropertyImplicit(String propertyName) => false;
-  String item(int index) => "";
+  // This can't call super(), since that's a factory constructor
+  EmptyStyleDeclaration()
+    : super._wrap(dom.document.createElement('div').style) {}

[Jacob, 2011/10/25 23:45:51]

wouldn't 
super._wrap(null);

be sufficient?

also, omit {} for empty constructor bodies.

[nweiz, 2011/10/26 00:27:37]

DOMWrapperBase assumes _ptr is non-null.

[Jacob, 2011/10/26 01:03:13]

I'd suggest adding an alternate 
_empty()
constructor  to DOMWrapperBase.
which sets _ptr to null.

[Anton Muhin, 2011/10/26 13:24:05]

Why it's needed?  I would really prefer not to have anything like that.

On 2011/10/26 01:03:13, jacobr wrote:

[nweiz, 2011/10/26 17:30:53]

I think it's useful to have this constructor wrap an empty style declaration
anyway; that was if new accessors are added EmptyStyleDeclaration doesn't break.

[Jacob, 2011/10/27 01:03:44]

I disagree with this reasoning because if the dummy style declaration created
here is ever used to set a property value (due to some hypothetical new
CSSStyleDeclaration method) then the behavior desired for this class will be
broken in surprising ways as now it would be possible to actually set styles
even though this class is supposed to be frozen.

Please create a new CL that fixes this issue.  

 
   void set cssText(String value) {
     throw new UnsupportedOperationException(
         "Can't modify a frozen style declaration.");
   }
 
   String removeProperty(String propertyName) {
     throw new UnsupportedOperationException(
         "Can't modify a frozen style declaration.");
   }
@@ skipping 233 matching lines @@
   void set title(String value) {
     throw new UnsupportedOperationException(
       "Title can't be set for document fragments.");
   }
 
   void set webkitdropzone(String value) {
     throw new UnsupportedOperationException(
       "WebKit drop zone can't be set for document fragments.");
   }
 }