This change makes all remaining tests use test.py's test_controller.js:
We have our own way of testing using test.py and that might change any time.
It's therefore not wise to rely on functionality in the unittest framework. If
we kept test_controller.js in the unittest package, we'd need to make a breaking
change whenever we change the behavior of test_controller.js. So this file was
forked into tools/testing/dart/test_controller.js.
After this, all our tests will use tools/testing/dart/test_controller.js. It is
therefore no longer necessary for the browser_controller to support the old
mechanism of posting back results. By removing this legacy code, we can ensure,
that the driving page of browser_controller will only react on valid messages
which were ment for it.
Context:
Some tests (e.g. dromaeo) might use postMessage internally, maybe even for
testing that postMessage is working. But the driving window should only react
on valid messages ment for it, ignoring any other messages.
R=blois@google.com, efortuna@google.com, ricow@google.com, whesse@google.com
Review URL: https://codereview.chromium.org//177333004
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@33365 260f80e4-7a28-3924-810f-c04153c831b5
Deletes:
pkg/shadow_dom
pkg/custom_element (except web_ui stuff)
pkg/html_import
Adds:
pkg/web_components, with README.md and build instructions
Changes:
pkg/html5lib -- deprecate queryAll/query in favor of *Selector
pkg/polymer -- test fixes & a few small changes to work with new polyfills, mostly in build
tests/html/custom -- can't load the CE polyfill at runtime, must now be injected statically via an HTML page, similar to the style @blois used for some custom element tests.
R=blois@google.com, sigmund@google.com
Review URL: https://codereview.chromium.org//158083002
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@32533 260f80e4-7a28-3924-810f-c04153c831b5
kevmoo@google.com