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] Site not readable and responsive on mobile devices #114

Closed
1 task done
asrvd opened this issue Mar 25, 2023 · 3 comments
Closed
1 task done

[Bug] Site not readable and responsive on mobile devices #114

asrvd opened this issue Mar 25, 2023 · 3 comments
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents ⛔️ status: discarded Will not be worked on

Comments

@asrvd
Copy link

asrvd commented Mar 25, 2023

Description

The current site is readable nicely on large devices but the text is not readable because of very small size on mobile devices (unless zoomed enough), these are responsive issues which can be solved easily by using some CSS. This also affects the accessibility of the site.

Reproduction

  1. Visit https://resources.creativecommons.org on a mobile device.

Expectation

The site is expected to adjust the positioning and sizing of elements according to screen size for better accessibility.
The issue arises because of the resource cards taking most of the space and font sizes not being adjusted according to screen size. The expected solution would be to use CSS grids for organizing the resource cards and adding some media queries to the CSS file.

Screenshots

image

Resolution

  • I would be interested in resolving this bug.
@asrvd asrvd 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 Mar 25, 2023
@asrvd
Copy link
Author

asrvd commented Mar 25, 2023

@possumbilities would like to have your thoughts on this and #113 , thank you 😸

@justaskulkarni
Copy link
Contributor

Issues #26 and #73 are pretty much the same since they all are related to responsiveness.

@possumbilities
Copy link
Contributor

this is a duplicate, please move conversations to the mentioned Issues.

@possumbilities possumbilities closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2023
@possumbilities possumbilities added ⛔️ status: discarded Will not be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Mar 31, 2023
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: high Stalls work on the project or its dependents ⛔️ status: discarded Will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants