BUG= http://dartbug.com/20809
The following files were not migrated, they used to be in platform.js
and are like polyfills, but are adding non-html spec functionality used
by polymer:
src/declaration/mdv.js
src/declaration/polymer.js
src/declaration/queue.js
src/declaration/styles.js
src/lib/dom.js
src/lib/lang.js
src/lib/loader.js
src/lib/styleloader.js
src/lib/url.js
src/system/compat.js
src/system/microtask.js
src/system/module.js
src/system/patches-mdv.js
src/system/unresolved.js
The following tests were not migrated. For the most part they are just
testing the features added by the files above:
test/html/loader-deduplicate.html
test/html/mdv-shadow.html
test/html/mdv-tests/polymer-expressions-tests.js
test/html/styling/recursive-style-import.html
test/html/url.html
test/js/bindMDV.js
test/js/oop.js
test/html/styling/rules/*
test/js/styling.js
test/js/register.js
test/js/utils.js
test/html/template-repeat-wrappers.html
R=sigmund@google.com
Review URL: https://codereview.chromium.org//558673004
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@40120 260f80e4-7a28-3924-810f-c04153c831b5
Two big things this enables:
* elements themselves can be data bound
* anything jsify can handle, including Dart functions. This means as we get @Export and such, it will be possible to bind those Dart types directly into JS elements. With that we can make things like <core-style> much nicer to use.
This also removes ported code from https://github.com/Polymer/NodeBind except for interfaces, since we don't need it anymore.
Added a Polymer test to verify it works for the typical end-to-end case. This uncovered the "deliver" method that needs to be there on Bindable.
Finally one Node.bind test depends on https://github.com/Polymer/ShadowDOM/pull/462, which fixes an issue where SD polyfill doesn't wrap an API used by Node.bind. Apparently no one has ever hit this on the JS side (the Dart port was immune, because our treatment of HTMLCollection is better).
R=sigmund@google.com
Review URL: https://codereview.chromium.org//355133002
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@38051 260f80e4-7a28-3924-810f-c04153c831b5
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
The biggest changes are in pkg:observe where we picked up a lot of optimizations to PathObserver/CompoundObserver.
template_binding gets one-time bindings, synchronous expansion, and lightweight "bindable" objects.
The tests are heavily refactored to use Future instead of the hacky observeTest/performMicrotaskCheckpoint pattern (I have been slowly changing the style for new tests, but observe-js made the change for all of them. yay!). Oh and the performMC stuff is gone from pkg:observe now.
There's also a new pkg:polymer feature for observation, which was ported so we are at a consistent baseline. (http://www.polymer-project.org/polymer.html#observeblock)
R=justinfagnani@google.com, sigmund@google.com
Review URL: https://codereview.chromium.org//132403010
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@32342 260f80e4-7a28-3924-810f-c04153c831b5
This CL will:
- fix a bug in the legacy AnalyzerCommandOutputImpl class (in certain cases
we did not report that the analyzer was missing a warning).
- make the outcome of running the analyzer on a test be one of:
* CompileTimeError
* MissingCompileTimeError
* StaticWarning
* MissingStaticWarning
- Make status file updates using the new Expectation markers
- Remove support for '@static-clean':
Previously running the analyer on a test could either result in
'Pass' or in 'Fail'. The '@static-clean' annotation has been used
as a (poor) mechanism to distinguish between errors and warnings.
Having the 4 markers mentioned above means we can remove '@static-clean'
- Remove 100 lines of rotted legacy code in our testing scripts.
- Make a status file entry for every test that has analyzer errors or warnings
R=ricow@google.com
Review URL: https://codereview.chromium.org//46163002
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@29350 260f80e4-7a28-3924-810f-c04153c831b5
sigmund@google.com