Skip to content
This repository has been archived by the owner on May 21, 2021. It is now read-only.


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

w11k-select - Single- and Multi-Select Directive for AngularJS

w11k-select is an AngularJS directive created to replace the default HTML select element which has a poor usability for most use cases particularly in desktop browsers.


  • Single- and multi-select
  • High performance and usability even with hundreds of options
  • Filter options to find the right one quickly
  • Uses Twitter Bootstrap markup / styling, comes with default css but easy to adjust / override
  • Disabled state and required-validation
  • Customisable texts (placeholders and selected representation)

Documentation and Demo

See Project Website at


  • Install via Bower (w11k-select) or download manually from our release repository (
  • Include scripts into your application (w11k-select and dependencies):
    • AngularJS
    • w11k-dropdownToggle
    • w11k-select
    • font-awesome (optional)
  • Inject dist/w11k-select-option.tpl.html and dist/w11k-select.tpl.html into your $templateCache
  • Add dependency to w11k-select to your angular module


<div w11k-select
     w11k-select-options="option.value as option.label for option in"

w11k-select-options is required and defines the html options elements that will be rendered within the html select element. This is similiar to the behavior of angular's ng-option directive. It follow the pattern of select as label for value in array.

w11k-select-config is optional and takes a config object or an array with config objects. The value is evaluated against the surrounding scope. If an array is given, all contained config object will be merged into one config object internally. Later config objects override values of previous config objects (like jQuery.extend or _.merge).

You can use different formats to specify the configuration. Some examples:

// reference an object or array from scope:

// define an object with an object literal:
w11k-select-config="{ required: true }"

// define an array via literal referencing an object from scope and define an object
w11k-select-config="[commonConfig, { multiple: false }]" 

Usage without font-awesome

font-awesome is an optional dependency of w11k-select. w11k-select uses font-awesome classes to show icons. If you don't want to include font-awesome in your project, you can use the following classes to style the icons / define their content. Otherwise they will be empty.

This is a sass example to reproduce the default icons. Notice: You don't need this code if you use font-awesome. The font-awesome classes are already included in the template of the directive.

.w11k-select .icon-deselect-all {
  @extend .fa;
  @extend .fa-times;
.w11k-select .icon-dropdown-open {
  @extend .fa;
  @extend .fa-chevron-up;
.w11k-select .icon-dropdown-closed {
  @extend .fa;
  @extend .fa-chevron-down;
.w11k-select .icon-select-filtered {
  @extend .fa;
  @extend .fa-check-square-o;
.w11k-select .icon-deselect-filtered {
  @extend .fa;
  @extend .fa-square-o;


  1. project
    1. create release branch
    2. npm run package
    3. bump bower version
    4. bump npm version (package.json & package-lock.json)
    5. update changelog
    6. merge release into develop and master branch
    7. git push --tags
  2. update demo page
    1. cd demo
    2. npm run build
    3. copy files to 'gh-pages' branch
  3. npm package
    1. npm publish
  4. bower package
    1. copy release to bower repo
    2. bump version in bower repo
    3. create tag in bower repo
    4. git push --tags


see milestones and issues at


MIT - see LICENSE file