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] Aside Navigation not responsive on screen sizes < 681px #271

Open
1 task done
egbadon-victor opened this issue Oct 20, 2024 · 2 comments
Open
1 task done
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@egbadon-victor
Copy link
Contributor

Description

For all pages that contain an aside navigation, the aside element maintains a padding that on screen sizes < 681px , make the navigation appear pushed to one side. This affects;

  • specimen/contexts/default-page.html
    - specimen/contexts/archive-page.html

Reproduction

  1. Fork and clone the repository to your local machine
  2. Open either the specimen/contexts/default-page.html or specimen/contexts/archive-page.html file on your browser
  3. Using the chrome developer tools, reduce the screen width to a size < 681px
  4. Observe the padding and apparent shifting of the element.

Expectation

The aside element should have uniform padding on the left and right side, and should not take too much space, so as to prioritize content.

Screenshots

image

Environment

  • Device: iPhone XR; laptop
  • OS: iOS 17; windows 11
  • Browser: Chrome
  • Other info: (eg. display resolution, ease-of-access settings)

Resolution

  • I would be interested in resolving this bug.
@egbadon-victor egbadon-victor 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 20, 2024
@possumbilities possumbilities added 🚧 status: blocked Blocked & therefore, not ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 22, 2024
@possumbilities
Copy link
Contributor

possumbilities commented Oct 22, 2024

I believe this is actually a result of #276, moving this to 🚧 status: blocked Blocked & therefore, not ready for work and once that's resolved IF it doesn't address this then we can unblock this.

@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed and removed 🟧 priority: high Stalls work on the project or its dependents labels Oct 22, 2024
@possumbilities possumbilities moved this from Triage to Backlog in possumbilities Oct 22, 2024
@egbadon-victor
Copy link
Contributor Author

@possumbilities this is noted.

But an alternative approach would be removing the left padding now, so that when an approach is decided for the content padding for mobile devices, it can be applied directly by any PR that resolves #276 .

Hence I can simply this issue to center around removing the left padding alone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

2 participants