[UI] Footer social links overflow out of container on small and desktop/tablet screens
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- scss
- Domain
- frontend
Research direction
Start by locating the footer styles and reproducing the overflow at tablet or narrow desktop widths. Check how the footer columns are sized and whether they can wrap within the container. Done when all four columns, including Socials, stay inside the footer at the affected widths.
Written by the indexing model from the issue text.
Description
URL
https://discuss.meshery.io/u/[username]/activity/replies
Current Behavior
On small and intermediate/narrow desktop viewports, the footer columns do not wrap into a secondary row. As a result, the 4th column (Socials) overflows horizontally beyond the right boundary of the footer container and spills onto the background.
Expected Behavior
Footer columns should wrap responsively (e.g., into a 2x2 grid or column stack) using flex-wrap: wrap and appropriate max-width sizing so that all sections, including Socials, remain fully within the footer container.
Steps to Reproduce
- Navigate to
https://discuss.meshery.io/u/[username]/activity/replies(or any discuss page). - Resize the browser window to a tablet or narrower desktop width (or inspect with responsive view).
- Scroll down to the footer.
- Notice the Socials column overflowing past the right edge of the dark footer container.
ScreenRecording
https://github.com/user-attachments/assets/a6769af6-9e9b-47b3-bfcf-5da96a427afa
- Dominant language
- SCSS
- Stars
- 17
- Forks
- 16
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from layer5io/discuss-theme
-
[Deprecation] Refactor deprecated .hbs component templates to .gjs formatPossibly taken @tejaswiverma121-byte claimed this 34 days ago. Openkind/bug
layer5io/discuss-theme#15 · 1 comment · 1 assignee ·
-
Navbar height shifts when search icon appears on scroll (layout shift)May be free again @sm-28601 claimed this 238 days ago, and no pull request is open. Openkind/bug
layer5io/discuss-theme#13 · 1 comment · 1 assignee ·
-
kind/enhancement
Difficulty 1/5 Under an hour Newbie friendliness 35/100
layer5io/discuss-theme#12 · 1 comment ·
-
[Feature] : Add a Callout Widget for the Playground on Discuss.Layer5.ioMay be free again @THEBOSS0369 claimed this 768 days ago, and no pull request is open. Openhelp wanted kind/enhancement language/javascript
Difficulty 5/5 Over a week Newbie friendliness 25/100
layer5io/discuss-theme#3 · 7 comments ·
All issues in layer5io/discuss-theme
Similar issues
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
db-ux-design-system/core-web#8613 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
killbill/killbill-admin-ui#672 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gchq/LD-Explorer#286 ·
Maintainers usually reply within 1 day