-
Notifications
You must be signed in to change notification settings - Fork 97
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
feat(back-to-top): pf-back-to-top element #2589
Conversation
🦋 Changeset detectedLatest commit: 16a5dba The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for patternfly-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
on the assumption that Nikki's earlier notes were addressed by Steven's patches, merging now to enable us to release 2.5.0 on time.
Merging ahead of 2.5.0. @nikkimk @hellogreg please open new issues for anything that comes up |
What I did
<pf-back-to-top>
elementTodo
Determine accessibility improvementsA href attribute and using a<a>
in shadowdom is warranted as expected. Can still use button version but there is caveat of owning accessibility in implementation, such as setting focus on element scrolled to.Figure out improvements for how a user hooks up element to "returning to top". PFv4 doesn't make assumptions on how the button is hooked up. We may opt for aSee above,href
attribute and use a link instead of a button when present, and definitely have to add a event when button is clicked otherwise for implementors to hook into.href
implementationTesting Instructions
Notes to Reviewers