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: consider dropping href="#" for disabled buttons since it is an invalid fragment id #9149

Closed
chalin opened this issue Nov 9, 2021 · 2 comments · Fixed by #9191

Comments

@chalin
Copy link
Contributor

chalin commented Nov 9, 2021

Great update in #8602 @jmooring!

Could we drop the invalid anchors (href="#") for disabled buttons?

<a href="#" aria-disabled="true" ...>

It's tripping link checking. For example, see

<a href="#" aria-disabled="true" aria-label="First" class="page-link" role="button" tabindex="-1"><span aria-hidden="true">&laquo;&laquo;</span></a>

Prior to #8602, the previous button omitted the href attribute when there was no previous page.

/cc @austinlparker @nate-double-u

@chalin chalin changed the title Pagination: consider dropping href="#" for disabled buttons since it is an invalid anchor Pagination: consider dropping href="#" for disabled buttons since it is an invalid reference Nov 9, 2021
@chalin chalin changed the title Pagination: consider dropping href="#" for disabled buttons since it is an invalid reference Pagination: consider dropping href="#" for disabled buttons since it is an invalid fragment id Nov 9, 2021
@jmooring
Copy link
Member

jmooring commented Nov 9, 2021

@chalin Yes, I will look at this. Link checking is one problem, but the primary driver is that the fragment resolves to the server root when serving from a subdirectory with a <base href="{{ site.BaseURL }}"> element.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants