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

[docs][bug] <rh-back-to-top> invisible in three demos #2111

Open
adamjohnson opened this issue Jan 8, 2025 · 1 comment · May be fixed by #2133
Open

[docs][bug] <rh-back-to-top> invisible in three demos #2111

adamjohnson opened this issue Jan 8, 2025 · 1 comment · May be fixed by #2133
Assignees
Labels
bug Something isn't working docs Improvements or additions to documentation

Comments

@adamjohnson
Copy link
Collaborator

adamjohnson commented Jan 8, 2025

Description

<rh-back-to-top> is invisible / not displaying in three of its demos:

  1. <rh-back-to-top> demo
    • This may be expected behavior. If it is, to the user it feels like a broken component (since it's invisible)
  2. Position Sticky Demo
  3. Warnings demo

Steps to reproduce

  1. Visit any of the links above in one of the browsers listed below
  2. Look for <rh-back-to-top>.

Expected behavior

<rh-back-to-top> should be visible in the demos listed above.

Operating System (OS)

macOS

Browsers

Safari, Microsoft Edge, Firefox

@adamjohnson adamjohnson added bug Something isn't working docs Improvements or additions to documentation labels Jan 8, 2025
@bennypowers
Copy link
Member

We should add content to the demos and have the first paragraph contain instructions in bold "scroll down to reveal the back to top element"

@adamjohnson adamjohnson moved this from Backlog to Review 🔍 in Red Hat Design System Jan 16, 2025
@adamjohnson adamjohnson self-assigned this Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working docs Improvements or additions to documentation
Projects
Status: Review 🔍
Development

Successfully merging a pull request may close this issue.

2 participants