WebUI styleguide: Update guidance about on-click vs on-tap handlers.
Bug: 812035
Change-Id: I319cf6149c4bfaac2751687c433a5546be86d116
Reviewed-on: https://chromium-review.googlesource.com/c/1469072
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Dan Beam <dbeam@chromium.org>
Commit-Queue: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631849}diff --git a/styleguide/web/web.md b/styleguide/web/web.md
index 56230a7..3544dd5 100644
--- a/styleguide/web/web.md
+++ b/styleguide/web/web.md
@@ -351,11 +351,7 @@
* DO: `Object<T>`
* DON'T: `Object<string, T>`
-### Events
-* Use Polymer's `on-tap` for click events instead of `on-click`
- * `on-tap` handlers should use `stopPropagation()` to prevent parents from
- handling the event where appropriate.
<div class="note">
Calling <code>stopPropagation()</code> from an <code>on-tap</code> handler will
@@ -384,6 +380,10 @@
This makes changing the type of `this.foo` easier (as the `@type` is
duplicated in less places, i.e. `@param`).
+* Use native `on-click` for click events instead of `on-tap`. 'tap' is a
+ synthetic event provided by Polymer for backward compatibility with some
+ browsers and is not needed by Chrome.
+
```js
properties: {
foo: {type: Number, observer: 'fooChanged_'}
