Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pagination: buggy first/previous/next/last logic #668

Closed
pixelastic opened this issue Nov 19, 2015 · 5 comments
Closed

pagination: buggy first/previous/next/last logic #668

pixelastic opened this issue Nov 19, 2015 · 5 comments
Assignees

Comments

@pixelastic
Copy link
Contributor

I feel like the logic used to hide/show the various previous/first/next/last links is buggy. Here are some screenshots:

image
^ I'm on the first page, everything is alright.

image
^ I'm on the second page, I don't think the "<<" (first page) link is needed (redundant with "<" previous)

image
^ 4th page, everything is alright

image
^ 5th page, oops the 6th page link disappeared. And I have both next and last (last might be useless here, and related to #594)

@vvo
Copy link
Contributor

vvo commented Nov 19, 2015

I think, the 6th page disappearing is a bug we need to fix (bug)

As for the "I am on second page", we should keep showing the <<, not really a big deal nor something we should again weight our preference I feel.

Others are good as you said

@Shipow
Copy link
Contributor

Shipow commented Nov 19, 2015

Some thoughts because obvious always win:

  • It's not recommended to use only icons most of the time so plain text 'previous', 'first', .. should be default.
  • it's not recommended to hide elements from an ui, so visible + disabled should be the default.
  • the current representation does not inform about the total pages (and when all pages are displayed first/last links are redondant, useless and even confusing when not labelled.
  • There is a lot of different config for pagination, no silver bullet, it really depends of the usecase.
  • I'm personally more often attracted by ellipsis solution (always show 3 first pages, and last one)

@bobylito
Copy link
Contributor

Ok let's fix the obvious bug then :)

@pixelastic
Copy link
Contributor Author

Ok, let's keep this issue focused on the 6th page bug then. We'll have to discuss a bit more to see how we want to tackle the other pagination UI questions

@bobylito bobylito self-assigned this Nov 19, 2015
bobylito pushed a commit that referenced this issue Nov 23, 2015
Also code simplification
@bobylito
Copy link
Contributor

Pull request is here : #675

pixelastic added a commit that referenced this issue Nov 23, 2015
fix(pagination): fix #668 edge case
vvo pushed a commit that referenced this issue Nov 25, 2015
<a name="1.1.0-beta"></a>
# [1.1.0-beta](v1.0.0...v1.1.0-beta) (2015-11-25)

### Bug Fixes

* **pagination:** fix #668 edge case ([d8f1196](d8f1196)), closes [#668](#668)
* **priceRanges:** Remove round from first range ([bf82395](bf82395))
* **starRating:** Retrieve the correct count and use numericRefinement ([f00ce38](f00ce38)), closes [#615](#615)

### Features

* **hierarchical:** expose rootPath and showParentLevel ([6e9bb7c](6e9bb7c))
vvo pushed a commit that referenced this issue Nov 26, 2015
<a name="1.1.0"></a>
# [1.1.0](v1.0.0...v1.1.0) (2015-11-26)

### Bug Fixes

* **pagination:** fix #668 edge case ([d8f1196](d8f1196)), closes [#668](#668)
* **priceRanges:** Remove round from first range ([bf82395](bf82395))
* **slider:** hide the slider when stats.min=stats.max ([42e4b64](42e4b64))
* **starRating:** Retrieve the correct count and use numericRefinement ([f00ce38](f00ce38)), closes [#615](#615)

### Features

* **hierarchical:** expose rootPath and showParentLevel ([6e9bb7c](6e9bb7c))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants