Fix custom element registry define test

The test relies on DOM elements with ids beind added as properties of the window. Servo does not do this, and this is not a best practice.
servo · bors-servo · Jun 5, 2017 · May 11, 2017 · May 30, 2017 · May 30, 2017
commit 1800da779c49b30f5b20d6e238bfe430e3377338
diff --git a/tests/wpt/metadata/MANIFEST.json b/tests/wpt/metadata/MANIFEST.json

    "testharness"
   ],
   "custom-elements/custom-element-registry/define.html": [
-   "724060b276a1f3254fd226e329631005ec5a5e87",
+   "4f3d4da1aae8efab035a4b951147904d71e7de3b",
    "testharness"
   ],
   "custom-elements/disconnected-callbacks.html": [
diff --git a/tests/wpt/web-platform-tests/custom-elements/custom-element-registry/define.html b/tests/wpt/web-platform-tests/custom-elements/custom-element-registry/define.html
@@ -12,6 +12,7 @@
   // https://html.spec.whatwg.org/multipage/scripting.html#element-definition
 
   // Use window from iframe to isolate the test.
+  const iframe = document.getElementById("iframe");
   const testWindow = iframe.contentDocument.defaultView;
   const customElements = testWindow.customElements;