Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(109)

Unified Diff: third_party/polymer/v1_0/components-chromium/iron-a11y-keys-behavior/README.md

Issue 1834313003: Remove unneeded files from third_party/polymer. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Restore bower.json files. Created 4 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/polymer/v1_0/components-chromium/iron-a11y-keys-behavior/README.md
diff --git a/third_party/polymer/v1_0/components-chromium/iron-a11y-keys-behavior/README.md b/third_party/polymer/v1_0/components-chromium/iron-a11y-keys-behavior/README.md
deleted file mode 100644
index f527af9d0b4e1f6db1b3b3a98e3c02ed04d93cca..0000000000000000000000000000000000000000
--- a/third_party/polymer/v1_0/components-chromium/iron-a11y-keys-behavior/README.md
+++ /dev/null
@@ -1,33 +0,0 @@
-
-<!---
-
-This README is automatically generated from the comments in these files:
-iron-a11y-keys-behavior.html
-
-Edit those files, and our readme bot will duplicate them over here!
-Edit this file, and the bot will squash your changes :)
-
--->
-
-[![Build Status](https://travis-ci.org/PolymerElements/iron-a11y-keys-behavior.svg?branch=master)](https://travis-ci.org/PolymerElements/iron-a11y-keys-behavior)
-
-_[Demo and API Docs](https://elements.polymer-project.org/elements/iron-a11y-keys-behavior)_
-
-
-##Polymer.IronA11yKeysBehavior
-
-
-`Polymer.IronA11yKeysBehavior` provides a normalized interface for processing
-keyboard commands that pertain to [WAI-ARIA best practices](http://www.w3.org/TR/wai-aria-practices/#kbd_general_binding).
-The element takes care of browser differences with respect to Keyboard events
-and uses an expressive syntax to filter key presses.
-
-Use the `keyBindings` prototype property to express what combination of keys
-will trigger the event to fire.
-
-Use the `key-event-target` attribute to set up event handlers on a specific
-node.
-The `keys-pressed` event will fire when one of the key combinations set with the
-`keys` property is pressed.
-
-

Powered by Google App Engine
This is Rietveld 408576698