Directory

← Back

nebula-select

Manage keyboard accessibility for a selection of controls.

Author

Contributors

Rating

[ This description is mirrored from README.md at github.com/arsnebula/nebula-select on 2019-05-22 ]

Published on webcomponents.org Polymer Version Sauce Labs Build Status Gitter Chat Become a Patreon

<nebula-select>

Manage keyboard accessibility for a group of controls.

  • Supports selecting controls from a nested hierarchy of elements
  • Enables using HOME, END, and the ARROW keys to navigate between controls in the group
  • Automatically ignores disabled and hidden elements
  • Provides easy access to the current selected element
  • Supports WAI-ARIA authoring practices for a11y

Installation

$ bower install -S arsnebula/nebula-select

Getting Started

Import the element.

<link rel="import" href="/bower_components/nebula-select/nebula-select.html"> 

Add the element.

<nebula-select selector='a' selected="{{selected}}" on-selected-changed="_onSelectedChanged" role="toolbar">
  <a href="#">Link 1</a>
  <a href="#">Link 2</a>
  <a href="#">Link 3</a>
</nebula-select>

Style the selected element using the selected attribute. The default attribute is selected, but you can customize the attribute name used by setting the selectedAttribute property.

nebula-select a[selected] {
  background-color: dimgrey;
  color: white;
}

For more information, see 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 or directly on GitHub.

  • Submit a feature request, or a defect report on the Issues List.

  • Become a Patreon. It takes a lot of time and effort to develop, document, test and support the elements in our 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

License

See LICENSE

Compatibility

(Loading compatibility data...)

Was this helpful? Need more help?
Leave a comment or a question below. You can also join the chat on Discord or ask questions on StackOverflow.

Version

Dependencies

  • polymer#Polymer/polymer#>=2.0.0-rc.1 <3.0
  • nebula-element-mixin#arsnebula/nebula-element-mixin#^2.0.0
Released
2017-04-19
Maturity
IMPORTED
License
ISC License

Compatibility

Framework
Polymer 1.0+
Polymer 2.0+
Browser
Browser Independent
Online