Andrew Joslin 3c15b118ca fix(activator): properly activate elements nested inside an item. ...

Addresses #1373.

Before: if an `<a>`, `ng-click`, or `<button>` inside of a .item,
was clicked, the activator would walk up .item and activate it.

Now:  If an `<a>`, `ng-click`, or `<button>` inside of a
.item is clicked, the activator will activate that element.

Additionally, CSS was added so `a.item-content.activated` would look
activated.

2014-05-13 08:56:37 -06:00

..

angular

test(ionCheckbox): add ngChange test

2014-05-13 07:24:32 -06:00

controllers

refactor(): reorganize source files

2014-04-14 10:47:27 -06:00

utils

fix(activator): properly activate elements nested inside an item.

2014-05-13 08:56:37 -06:00

views

scrollview test hax

2014-05-12 14:55:10 -05:00

events.unit.js

chore(build): add cloud e2e/unit tests

2014-02-21 11:22:23 -05:00