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.

Sign up for GitHub

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

Jump to bottom

Opposite direction arrow button for Omnibar #10240

Open
Craig-Rosario opened this issue Dec 31, 2024 · 2 comments
Open

Opposite direction arrow button for Omnibar #10240

Craig-Rosario opened this issue Dec 31, 2024 · 2 comments
Assignees
@Craig-Rosario
Labels
Good First Issue Easy issue. Good for newcomers. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Module: Books Page Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]

Comments

@Craig-Rosario
Copy link
Contributor

Craig-Rosario commented Dec 31, 2024 •
edited
Loading

Proposal

Currently, in the book section, when users are selecting different sections, they are only provided with an arrow for navigation in one direction. (eg. go to https://openlibrary.org/works/OL40939W/The_Secret_Language_of_Birthdays and resize the page for the arrow to appear).

As per the discussion with @cdrini, adding an arrow for the opposite direction would significantly improve the functionality and overall user experience.

Current layout:
image

Proposed feature:
Adding another arrow for the opposite direction
image

Justification

Problem: Users can currently only navigate in one direction in the book section, limiting navigation flexibility.

Impact: Adding a backward navigation arrow will improve user experience and functionality by enabling movement between sections.

Status: I am currently working on implementing this feature.

Breakdown

Requirements Checklist

  • [ ]

Related files

Stakeholders

Instructions for Contributors

Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.
@Craig-Rosario Craig-Rosario added Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] labels Dec 31, 2024
@Craig-Rosario
Copy link
Contributor Author

@BHAV0207 as you can see in the status, I'm currently working on this issue

@BHAV0207
Copy link

BHAV0207 commented Jan 3, 2025 •
edited
Loading

@Craig-Rosario understood , sorry didn't saw that

@github-actions github-actions bot added the Needs: Response Issues which require feedback from lead label Jan 3, 2025
@mekarpeles mekarpeles added Good First Issue Easy issue. Good for newcomers. [managed] Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Module: Books Page and removed Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Lead Needs: Response Issues which require feedback from lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Craig-Rosario Craig-Rosario

Labels
Good First Issue Easy issue. Good for newcomers. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Module: Books Page Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mekarpeles @BHAV0207 @Craig-Rosario