Closes#1076
If the user for example switches tabs,
$ionicNavBarDelegate.getPreviousTitle() will return the title from the
navbar within the previous tab. In this case, the back button will not
be shown. To not use the previous title in a case like this, you can
now do:
```js
var shouldShowTitle = $ionicNavBarDelegate.showBackButton();
if (shouldShowTitle) {
$scope.previousTitle = $ionicNavBarDelegate.getPreviousTitle();
}
```
BREAKING CHANGE: The developer should be stating exactly how an icon
should show, but previously the right nav arrow icon violates this by
automatically showing a right arrow when an item was an anchor or
button. Instead of using the `:after` item selector, which was always
applied by default, it uses the same markup as `item-icon-right`, which
is easier to understand, customizable and not a hard coded default.
This change removes the `:after` nav icon styling, and creates a new
class, `icon-accessory`, based off of similar CSS. The change makes a
nav arrow highly customizable, allows RTL developers to easily control
the arrow direction, and the accessory class is something that's
reusable.
An example of right side arrow using `ion-chevron-right` as the icon:
<a class="item item-icon-right" href="#">
Check mail
<i class="icon ion-chevron-right icon-accessory"></i>
</a>
Now you can do:
```
<div class="row row-stretch">
<div class="col">Very<br />Much<br />Text<br /></div>
<div class="col">Short</div>
<div class="col">Shrt</div>
</div>
```
All columns will have equal heights. Especially useful when 'simulating' tables with the grid system.
Previously I disabled the activation class immediately on a touchmove,
where as the click will still work if you touchstart and touchend
within a few pixels of each other. So visually it may have looked like
the click shouldn't have worked. I just updated it so the use the same
numbers. For example, if you hold down an item and move just 5 pixels,
the item will stay active (before it wouldn't have), and the click will
fire. But at the same time, if you hold down an item, and move a larger
distance, once it realizes that it went farther than 6 pixels it'll not
allow a click to happen, AND it'll not show the item as being active.
The link to the relevant documentation on the header bar [1.0.0-beta.1 (2014-03-25)] was missing a "d". This caused it to return a 404 "Page not found" whenever it was clicked.