update custom elements and shadow dom

update custom elements and shadow dom

R=blois@google.com

Committed: https://code.google.com/p/dart/source/detail?r=32171

[Jennifer Messerly, 2014-01-27 19:44:31]

Seems to be working across Dartium/Chrome/FF/Safari.

note that some things that used to run under native custom elements on Chrome
now run with the polyfill, hence the html.status change.

https://codereview.chromium.org/140853005/diff/1/pkg/unittest/lib/html_config...
File pkg/unittest/lib/html_config.dart (left):

https://codereview.chromium.org/140853005/diff/1/pkg/unittest/lib/html_config...
pkg/unittest/lib/html_config.dart:169: window.postMessage('unittest-suite-done',
'*');
Without this fix, test failures were showing up as "PASS" in dev tools, and
producing a warning at the command line that the test emitted "PASS" and "FAIL".
They were correctly recorded as a failure, though.

[blois, 2014-01-27 20:20:25]

lgtm (though take a look at IE)

FYI- for tracking the github rev in third_party/pkg, I'm just checking in a
REVISION file which just has the hash- a bit easier than including it in the CL
comments.

https://codereview.chromium.org/140853005/diff/1/pkg/custom_element/lib/custo...
File pkg/custom_element/lib/custom-elements.debug.js (left):

https://codereview.chromium.org/140853005/diff/1/pkg/custom_element/lib/custo...
pkg/custom_element/lib/custom-elements.debug.js:59: (function(global) {
Looks like the MutationObserver polyfill is external- do tests need to be
updated to load it for IE9?

[blois, 2014-01-28 00:15:26]

https://codereview.chromium.org/140853005/diff/1/tools/dom/src/dart2js_Custom...
File tools/dom/src/dart2js_CustomElementSupport.dart (right):

https://codereview.chromium.org/140853005/diff/1/tools/dom/src/dart2js_Custom...
tools/dom/src/dart2js_CustomElementSupport.dart:102: JS('void',
'#.attachedCallback = #', properties,
Can keep both enteredView and attachedCallback until we move to 33. Just open a
bug to remove old behavior.

[Jennifer Messerly, 2014-01-29 20:52:36]

Good idea about the REVISION file, will switch to that.

https://codereview.chromium.org/140853005/diff/1/pkg/custom_element/lib/custo...
File pkg/custom_element/lib/custom-elements.debug.js (left):

https://codereview.chromium.org/140853005/diff/1/pkg/custom_element/lib/custo...
pkg/custom_element/lib/custom-elements.debug.js:59: (function(global) {
On 2014/01/27 20:20:26, blois wrote:
> Looks like the MutationObserver polyfill is external- do tests need to be
> updated to load it for IE9?

good catch! will fix that in the tests

https://codereview.chromium.org/140853005/diff/1/tools/dom/src/dart2js_Custom...
File tools/dom/src/dart2js_CustomElementSupport.dart (right):

https://codereview.chromium.org/140853005/diff/1/tools/dom/src/dart2js_Custom...
tools/dom/src/dart2js_CustomElementSupport.dart:102: JS('void',
'#.attachedCallback = #', properties,
On 2014/01/28 00:15:27, blois wrote:
> Can keep both enteredView and attachedCallback until we move to 33. Just open
a
> bug to remove old behavior.

chatted in person, I think with registerElement we only need to set the new
callback names. Fortunately the callbacks were renamed at the same time as
document.register

[Jennifer Messerly, 2014-01-29 23:47:21]

PTAL. now has revisions file & mutation observers fallback

[blois, 2014-01-29 23:52:59]

lgtm

[Jennifer Messerly, 2014-01-30 20:56:35]

Committed patchset #3 manually as r32171 (presubmit successful).