Do not delete DOMStringMap and DOMStringList types from idl database.

lib/dom/src/native_DOMImplementation.dart

Index: lib/dom/src/native_DOMImplementation.dart
diff --git a/lib/dom/src/native_DOMImplementation.dart b/lib/dom/src/native_DOMImplementation.dart
index aa0a3ccca2aebd3ef3eef8d7bcc8f9f7e0b7c99f..048fedb8494cd4feacc099d979afaadfbde75545 100644
--- a/lib/dom/src/native_DOMImplementation.dart
+++ b/lib/dom/src/native_DOMImplementation.dart
@@ -79,7 +79,7 @@ class LocationCrossFrameImplementation extends DOMWrapperBase implements Locatio
   String get typeName() => "Location";
 }
 
-class DOMStringMapImplementation extends DOMWrapperBase implements Map<String, String> {
+class DOMStringMapImplementation extends DOMWrapperBase implements DOMStringMap {

[Anton Muhin, 2012/04/13 16:46:34]

don't you have to add DOMStringListImplementation at least here?

[podivilov, 2012/04/13 16:49:26]

Could you please clarify? We need to add DOMStringListImplementation class at
some point, but this change is pure refactoring.

[Anton Muhin, 2012/04/13 16:51:18]

I don't think it's a good idea to stop removing DOMStringList, but not prove
implementation class for it.  Esp. given the fact that to add
DOMStringListInplmpl will take rougly 10--15 lines of code.

On 2012/04/13 16:49:26, podivilov wrote:

[podivilov, 2012/04/13 17:00:53]

The problem with it is that we'll have to provide a c++ implementation as well,
which is many more lines and better done as a separate cl.

If you think unused DOMStringList interface that appeared as a side-effect of
this change is a problem, I could leave DOMStringList part as is for now.

[Anton Muhin, 2012/04/13 17:08:56]

Whatever you prefer.

On 2012/04/13 17:00:53, podivilov wrote:

   static DOMStringMapImplementation _createDOMStringMapImplementation() => new DOMStringMapImplementation._createDOMStringMapImplementation();
   DOMStringMapImplementation._createDOMStringMapImplementation();