About the nebula-inputbox category

Directory nebula-inputbox
1

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

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

<nebula-inputbox>

Add labels and hints to an input control.

  • Provides named slots to add hints around a standard input control
  • Easily styled with CSS variables and mixins.

Installation

$ bower install -S arsnebula/nebula-inputbox

Getting Started

Import the element:

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

Add the element. The main input slot should contain a normal HTML input control. Add hints such as labels, icons and help or validation text around the input control, using the top, left, right and bottom named slots.

<nebula-inputbox>
  <input slot="input" id="email" name="email" type="text" autocomplete="off" />
  <label slot="top" for="email">Email</label>
  <iron-icon icon="icons:mail" slot="left"></iron-icon>
  <iron-icon icon="icons:search" slot="right"></iron-icon>
  <div slot="bottom">An email for account verification</div>  
</nebula-inputbox>

You can easily theme the element using slot and other attributes.

nebula-inputbox[focused] {
  color: teal;
}
nebula-inputbox[invalid][slot=bottom] {
  color: darkred;
}

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