Workaround for https://crbug.com/178297 (HTMLMediaElement.play() can only be initiated by a user gesture on Android). Attaches a capturing event listener to document that calls play() with an empty src. This allows to future play() calls without direct user interaction.
Element dependencies are managed via Bower. You can install that via:
npm install -g bower
Then, go ahead and download the element's dependencies:
bower install
If you wish to lint your element, we recommend that you use Polylint to take into account Polymer linting specificities. You can install it via:
npm install -g polylint
And you can run it via:
polylint -i android-media-autoplay.html
If your element contains errors, they will appear on the console.
Note that it is possible to use Polylint with Atom and Sublime with the appropriate package/plugin.
For more options regarding polylint, please refer to the
documentation.
If you wish to work on your element in isolation, we recommend that you use Polyserve to keep your element's bower dependencies in line. You can install it via:
npm install -g polyserve
And you can run it via:
polyserve
Once running, you can preview your element at
http://localhost:8080/components/android-media-autoplay/, where android-media-autoplay is the name of the directory containing it.
Simply navigate to the /test directory of your element to run its tests. If
you are using Polyserve: http://localhost:8080/components/android-media-autoplay/test/
The tests are compatible with web-component-tester. Install it via:
npm install -g web-component-tester
Then, you can run your tests on all of your local browsers via:
wct
wct -l chrome will only run tests in chrome.
wct -p will keep the browsers alive after test runs (refresh to re-run).
wct test/some-file.html will test only the files you specify.
If you'd like to use Yeoman to scaffold your element that's possible. The official generator-polymer generator has a seed subgenerator.