[Bug 22192] New: [Custom]: Perhaps element's last completion value should not be from an exceptional termination?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22192

            Bug ID: 22192
           Summary: [Custom]: Perhaps element's last completion value
                    should not be from an exceptional termination?
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dominicc@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

"Let PROPERTIES be DOCUMENT's last completion value"

I think 'throw' establishes a completion value, so for example this:

<element name="sur-prise">
  <template>...</template>
  <script>
    var t = document.currentScript.parentElement.querySelectorAll('template');
    var defensiveCopy = t.content.cloneNode();
    ({
      readyCallback: function () {
        var root = this.createShadowRoot();
        root.appendChild(defensiveCopy.cloneNode());
      }
    });
  </script>
</element>

Will create a Custom Element with a prototype with 'message' and 'stack'
because those are the own properties of the exception generated at
t.content.cloneNode (because I "accidentally" did querySelectorAll instead of
querySelector, so t is a NodeList and t.content is undefined;
undefined.cloneNode() throws; etc.)

Maybe custom element processing should not set up this funkified prototype if
the script exits with an error exit?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 29 May 2013 05:45:37 UTC