Pagy next link for infinite-scroll

[rctneil]

I'm trying to use infinite-scroll and it expects a selector string for the next path. It also uses the existance of this selector to determine if the current page is the last one or not.

When pagy is on the last page the element gets aria-disabled="true". I then appended aria-disabled="false" to my current path selector but that doesn't exist.

I need a way to either:

1. Not show the Prev or Next links when they are not neccessary. (hiding them via CSS won't work here)

OR

2. Add aria-disabled="false" by default to all the links in the nav helper.

Any ideas?

[ddnexus]

I am confused: how would you use the "infinite-scroll" with "all the links in the nav helper" ... 🤔

[ddnexus]

No frustration at all. If you want the pagy_nav with infinite scrolling it's up to you.

[rctneil]

Yes, I understand that, but your pagy_nav helper outputs the following:

<nav class="pagy nav" aria-label="Pages"><a data-turbo-action="advance" href="/venues/attractions?page=104" aria-label="Previous">&lt;</a><a data-turbo-action="advance" href="/venues/attractions">1</a><a role="link" aria-disabled="true" class="gap">…</a><a data-turbo-action="advance" href="/venues/attractions?page=101">101</a><a data-turbo-action="advance" href="/venues/attractions?page=102">102</a><a data-turbo-action="advance" href="/venues/attractions?page=103">103</a><a data-turbo-action="advance" href="/venues/attractions?page=104">104</a><a role="link" aria-disabled="true" aria-current="page" class="current">105</a><a role="link" aria-disabled="true" aria-label="Next">&gt;</a></nav>

What I am asking is how do I output that but so the "<" and ">" links do not get output on the first and last pages? I do understand that my infinite scrolling setup is not to your liking, and that's absolutely fine. Right now it's what I have to work with.

Therefore, I need to know if there is an option or method I can use to stop those links from getting output on the first/last pages.

Whether my "infinite-scroll" is right or wrong in your opinion makes absolutely no difference to the issue here. I 110% agree that there are better ways (without using a 3rd party library), but right now, I have to use it and that's not the problem here.

The problem is the links output via your pagy_nav helper. Please can we just stick to the actual problem rather than the "right" or "wrong" ways of doing something.

Thankyou,
Neil

[ddnexus]

Please can we just stick to the actual problem ...

Yes, please do it next time! 🤣

A simple single-sentence post that sticks to the actual problem would be something like:

"How can I avoid to render the first and next links for the first and last page of a pagy_nav bar?"

And the answer would be:

"You can override the helper that generates them, or remove the specific tag with a line of JavaScript."

[rctneil]

I'm sorry but you do not have to be so rude. I effectively did ask that. I gave context as to why I needed the prev and next links removing but then you started discussing "better" ways of infinite scroll. You ignored answering the question. I gave two options in the first post and you didn't even mention them, even to say that neither were possible.

Ok, so...

Overriding the helper. I'm not crazy up in all this, what would be the best way to go about this? Could you please provide an example?

I do not wish to remove the links via javascript as I feel it's overkill to do it like that. Seems silly to add them and then remove via jabvascript, especially to ensure that is done before infinite-scroll looks at the page. Even then, I don't think JS runs for the pages requested by IS, therefore I do not think this approach is suitable.

Would it be possible to provide an option in the pagy initialiser that allows users to choose whether prev next links are output in the pagy_nav helper on first and last pages? Seems like a useful option to me?

Thank you for your fast responses.

[ddnexus]

I'm sorry but you do not have to be so rude.

Not rude, just funny 🤣

Would it be possible to provide an option in the pagy initialiser that allows users to choose whether prev next links are output in the pagy_nav helper on first and last pages?

It's already kind of implemented in the upcoming v43 but it currently don't work as you would like.