-
Notifications
You must be signed in to change notification settings - Fork 307
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
Feature request: Custom pagination elements #8
Comments
No, the plugin does not assume anchors. You can use whatever you like. Here are two examples using buttons instead of anchors: http://www.malsup.com/jquery/cycle/pager-button.html |
Yes, I know, but for example, |
Yes, that's a good point. But updateActivePagerLink can be overridden. Here's an example: http://jquery.malsup.com/cycle/pager7.html |
Thanks. That's exactly what I've been doing so far. But, since I believe this can be improved, hence my feature request :) One possible solution would be adding an option to specify the type of element you would like to use as pagination, being this an anchor by default. |
Hmm, maybe it makes sense to assume that immediate children of the nav element are the ones we care about. Would that work in your case? So instead of:
I would do this:
|
Sure, and it's still specific enough, imo. It works perfectly for me, thanks. By the way, I guess I've found a bug about overriding this function in the default opts. I'm creating an issue about it. Issue #10 created. |
I checked this fix into v2.83. |
Currently the plugin assumes using anchors as pagination elements but, since the pagination doesn't show up with Javascript disabled and for usability and semantics sake, I would prefer to use <button> type elements instead.
It's actually possible to use any element as a pagination one, but doing that, the plugin loses some of its functionality.
The text was updated successfully, but these errors were encountered: