You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Support request => Please do not submit support request here
Current behavior
when the `[(nzPageIndex)]` is `1`, click the previous button `<` will still emit a `nzPageIndexChange` event.
Expected behavior
i think it may be not necessary in this case. i use that event to make a request
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
Angular version: 4.3.0
ng-zorro-antd version: ^0.5.0-rc.4
Browser:
- [* ] Chrome (desktop) version 60.0.3112.113
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
For Tooling issues:
- Node version: v8.4.0
- Platform: Mac
Others:
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
lockbot
locked as resolved and limited conversation to collaborators
Feb 19, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm submitting a bug
Current behavior
when the `[(nzPageIndex)]` is `1`, click the previous button `<` will still emit a `nzPageIndexChange` event.
Expected behavior
i think it may be not necessary in this case. i use that event to make a request
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: