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

[Bug] Navbar Fails to Stick on Page Scroll #216

Open
1 task done
shivam8112005 opened this issue Oct 12, 2024 · 5 comments
Open
1 task done

[Bug] Navbar Fails to Stick on Page Scroll #216

shivam8112005 opened this issue Oct 12, 2024 · 5 comments
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@shivam8112005
Copy link

shivam8112005 commented Oct 12, 2024

Description

The sticky navbar fails to remain fixed at the top of the viewport when the user scrolls down the page, causing navigation links to become inaccessible.

Reproduction

  1. Open the web application in a supported browser.
  2. Scroll down the page.
  3. Observe that the navbar does not stick to the top of the viewport.
  4. See where the navbar vanishes with instead of remaining fixed.

Expectation

I expected the navbar to stay at the top of the viewport while scrolling, allowing continuous access to navigation links.

Screenshots

Screenshot 2024-10-12 174823

Environment

  • Device: laptop
  • OS: Windows 11
  • Browser: Chrome
  • Version: 94.0.4606.61
  • Other info: 1920x1080 resolution

Additional context

Resolution

  • I would be interested in resolving this bug.
@shivam8112005 shivam8112005 added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Oct 12, 2024
@cc-open-source-bot cc-open-source-bot moved this to Triage in Applications Oct 12, 2024
@rypptc
Copy link
Contributor

rypptc commented Oct 14, 2024

I'm not sure if this is an issue that should be done here, I see many cc pages have already a standard design. Probably, if the intention is having a fixed navbar, this should be done across all pages.

@Queen-codes
Copy link
Contributor

Hi @rypptc I agree with you. I think that's the expected behaviour of Vocabulary. @shivam8112005 however, if you think it's an improvement that Vocabulary will benefit from, I think it is better to raise this issue in vocabulary's repository. The mentors will go through it and decide.

@SisiVero
Copy link

I once opened a similar issue but it was discarded. I assume the current navbar format is what is needed for now.
@shivam8112005 .

@shivam8112005
Copy link
Author

ohk @rypptc i will consider it

@TimidRobot TimidRobot added 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 🕹 aspect: interface Concerns end-users' experience with the software and removed 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 💻 aspect: code Concerns the software code in the repository labels Oct 14, 2024
@TimidRobot
Copy link
Member

🚧 status: blocked Blocked & therefore, not ready for work pending:

@TimidRobot TimidRobot moved this from Triage to Backlog in Applications Oct 14, 2024
@TimidRobot TimidRobot moved this to Backlog in WebDev Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

5 participants