When a table is .table-striped, and a cell in a striped row has any contextual class, the background color of the striped row overwrite the contextual class background color.

Example code:

<table class="table table-striped">
  <tbody>
    <tr>
      <td class="success">Okay</td>
    </tr>
  </tbody>
</table>

Expected result:
The background of the the cell should be green (as per .success).

What happens:
The background of the cell is gray (as per .table-striped).

Add a Copy button next to each example in the docs.

The tooltip balloon should be removed when a DOM $destroy event is fired in the target element.

The native select <optgroup> is needed as a feature of the dropdown directive.

Plook does lookups to Bower services, so we don't need to do this ourselves during the docs deployment.
This way, we can drop the highly unstable Rawgit.

The assets/meta/icons-list.json file is right now being downloaded in every page.
Although it's a pretty small file, we should not waste bandwidth!

Off Canvas sidebars are so common in mobile systems.
We should have a directive that allows us to have them.

In a second moment, we could think about supporting swipes to toggle that sidebar.

List of desired features:

• Top/bottom/right sides (left should be the default)
• Sizes (tiny, small, normal, large, xlarge)
• Screen size targeted
• Touch ready (swipe events)

Right now, if we're allowed to select twice the same element in a dropdown with maxItems > 1.
This also causes items to not render after the repeated item.

A static navbar should work just like a fixed navbar, except that it shouldn't scroll with the page.

Allow buttons to have varying sizes, following the Frontkit patterns.
For example:

• xlarge
• large
• small
• tiny

Allow for positioning icons inside inputs, at the begining or at the end.

The tooltip directive should use delegation when binding its events.
This allows for various elements to be bound with the same options, which is the desired default in most cases, I believe.

Implement file upload element.
An idea: http://jasny.github.io/bootstrap/javascript/#fileinput

Ideas from Bootstrap: here and here.

• Implement button dropdown
• Implement button groups

Add Google Analytics code into the docs.

Dropdown options which were already selected should not show as available for selection.
They should be grayed out, looking like they are disabled.
Also, these options should not be accessible.

Because of this line,
@import frontkit.less in 3rd party code is just impossible.

We should use normalize.css as a bower dependency, and prepend it to the frontkit.css output via Grunt, not LESS.

Implement major ARIA attributes over docs html.
Should enhance accessibility.

Implement select form element.
A few plugins like the planned idea:

• Selectize
• Chosen
• Select2

Steps:

• Single item select
• Searching
• Keyboard integration

Implement CSSComb linting task.
I don't want it to change my output/sources, just lint .less files and output errors.

When I press the backspace key in a dropdown in Android, it does no effect.

Just like the buttons, which have varying size now (see #17), inputs should be allowed to have the same varying size classes.

Implement a directive for autogrowing textboxes

Examples of this idea:
http://www.polymer-project.org/components/paper-input/demo.html
http://www.jacklmoore.com/autosize/

A CONTRIBUTING.md file should be added to the repo.
It may contain at least the following:

• Tips on how to create a great issue
• Commit message style
• Code styles

An search input able to filter the icons list would be helpful.
Beyond just filtering icons list, the categories could be hidden if no icons match the typed search.

There are no references to the github repo in the docs except for the home page.

Implement a tooltip component.

Create a .text-* utility classes for available contexts:

• muted: disabled text
• success
• info
• warning
• danger

Since Angular 1.2.18, the dropdown items no longer show their text.
The fix may be the same as d933c8b

The dropdown-options directive has a items property.
This doesn't make any sense! We have another dropdown-items directive.

Allow home/end keys to navigate between options, going to the first/last option, respectively.

When a dropdown is full, it'll block any ctrl + key combo, where key is a visible char (any alphanumeric char, for example).

A component for displaying alerts/notifications in the style of Facebook/Gmail would be a great addition.
However, as their approaches use a floating element, probably something fixed to the content could be great as well, just like what Bootstrap did, for example.

Add a .editorconfig file to the project.

We should find out what browsers we must support and at what versions.
After this is done, document this in both readme and docs site.

Allow to change ordering of grid columns, moving them to the left or to the right.

When using arrow keys, we should be able to move the caret between selected items.
So if we have a selection "AC/DC", "Dio" and we press the left arrow key, the caret will be placed between the two items.
If we press the right arrow key, the caret will be placed after those items.

Normalize.css should not be referenced in our bower.json file.
This is because most times the user installing Frontkit via Bower is not going to need normalize.css unless using the source .less files.

A date/time/datetime picker would be very helpful until all browsers implement them.

Implement something like https://github.com/koppi/iso-country-flags-svg-collection, but plain SVG.

An .input should be allowed as a wrapper for form controls, while preserving the same styles.
This allows us to place additional visual elements inside an input component.

For example:

<div class="input">
    <input type="text">
</div>

should be the same as

<input type="text" class="input">

Document all utility classes:

• .pull-start/.pull-end
• .show/.hide
• .text-left/.text-center/.text-right/.text-justify

The mixins file is getting pretty big.
We probably should split it into various files, separated by their category.

For example:

• grid
• utilities
• css3/vendor prefix helpers
• etc

Dropdown is no longer working with Angular v1.2.18.
There's simply no transcluded content inside options.

See angular/angular.js#7842 for further info.

Our iconic font is right now missing an icon that represent a calendar, day or date.
It's probably a very common icon.

Headroom hides the navbar when scrolling down, and shows it when scrolling up, as a sign that the user is looking for it.

http://wicky.nillia.ms/headroom.js/

As a plus, it already has a Angular directive.