Pagination directive, IE11 issue with prev/next buttons

[scolt]

Bug description:

After click on disabled previous/next button application redirects user to home page.

Steps to reproduce via plunker below

1. Open home page in IE11 (Internet Explorer 11)
2. Click on "Pagination" link
3. Observe that previous button is disabled
4. Click on previous button

Actual result:
Home page is opened.

Expected result:
Nothing should happen.

Link to minimally-working plunker that reproduces the issue:

http://plnkr.co/edit/1QBjhagSpwAb5dvFtm6S?p=preview

Version of Angular, UIBS, and Bootstrap

Angular: 1.4.7

UIBS: 2.1.4

Bootstrap: 3.3.3

Recommendation for fixes

As I see, issue occurred because "href" is provided. This is empty attribute and in results it can be removed without any regression.

[roger2hk]

I am having the same issue and was about to create one.
The same issue happens in pager as well.
The fix is to remove those href in uib/template/pagination/pagination.html and uib/template/pager/pager.html.

I will now create a pull request.

[roger2hk]

I just realize removing the empty href would break the CSS. My current workaround is to change the empty href to href="/".

Here is the Plunker that fixed the issue by using href="/".
http://plnkr.co/edit/6shfJl7yL5OcURpMSuo8?p=preview

[wesleycho]

I need to verify my hypothesis at work tomorrow on a Windows VM with IE11, but I suspect this is a usage problem - this demo is not quite a minimal reproduction indicating it is an issue specifically with this library as it is polluted with ngRoute, and I have strong suspicions that that is actually the cause of this issue.

Please slim down the reproduction to not contain ngRoute if possible - otherwise, this is highly likely not a valid library issue, and thus filed in the wrong repository.

[roger2hk]

The same issue happens in ui-router as well. Hope my information helps.

[roger2hk]

@scolt There is another workaround before this issue is fixed.

According to the issue raised in ui-router, the workaround is to add a customized CSS. However, this would break the cursor: not-allowed; impacting the user experience.
angular-ui/ui-router#2957

.pagination > .disabled > a {
  pointer-events: none;
}

[wesleycho]

Created a minimal reproduction from the homepage here - the Plunker in the OP had other distractions/issues with it that would prevent proper fixing.