A Polymer mixin to support focus-related properties.
**[ This description is mirrored from README.md at [github.com/arsnebula/nebula-focus-behavior](https://github.com//arsnebula/nebula-focus-behavior/blob/v2.0.3/README.md) on 2019-05-10 ]**
[](https://www.webcomponents.org/element/arsnebula/nebula-focus-behavior)
[](https://www.polymer-project.org)
[](https://saucelabs.com/beta/builds/acf477bffcd14a41ba740b6570f608fe)
[](https://gitter.im/arsnebula/webcomponents)
[](https://www.patreon.com/arsnebula)
# \
A Polymer class extension mixin to enable a custom element with focus-related capabilities.
* Detects keyboard, mouse and touch user interaction modes
* Adds focus-related properties and attributes that can help style elements
* Normalizes a `focused` state for keyboard and mouse hover user interactions
* Solves the problem of **sticky focus** in touch screen environments
## Installation
```sh
$ bower install -S arsnebula/nebula-focus-behavior
```
## Usage
Import the package.
```html
```
Extend the base element using the mixin class factory method.
```js
class MyElement extends Nebula.FocusBehavior(Polymer.Element) {}
```
*For more information, refer to the API documentation.*
## Contributing
We welcome and appreciate feedback from the community. Here are a few ways that you can show your appreciation for this package:
* Give us a **Star on GitHub** from either [webcomponents.org](https://www.webcomponents.org/element/arsnebula/nebula-element-mixin) or directly on [GitHub](https://github.com/arsnebula/nebula-element-mixin).
* Submit a feature request, or a defect report on the [Issues List](https://www.webcomponents.org/element/arsnebula/nebula-element-mixin/issues).
* Become a [Patreon](https://www.patreon.com/arsnebula). It takes a lot of time and effort to develop, document, test and support the elements in our [Nebula Essentials](https://www.webcomponents.org/collection/arsnebula/nebula-essentials) collection. Your financial contribution will help ensure that our entire collection continues to grow and improve.
If you are a developer, and are interested in making a code contribution, consider opening an issue first to describe the change, and discuss with the core repository maintainers. Once you are ready, prepare a pull request:
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D
## Change Log
See [CHANGELOG](/CHANGELOG.md)
## License
See [LICENSE](/LICENSE.md)
