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

Refactored Wilma CSS for Better Responsiveness #4061

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

milospp
Copy link
Contributor

@milospp milospp commented Feb 28, 2025

VIVO GitHub issue

What does this pull request do?

Created breakpoints for smaller screen, so that smaller devices can

What's new?

Mobile optimised design(up to 320px width)
Avoided horizontal scroll

How should this be tested?

Open every page and test by resizing up to around 400px in width (Mobile device toolbar can be used in Google Chrome to simulate phone display or ViewPort resizer extension)

Additional Notes:

Here is the video example

  • The Left window is VIVO with old Wilma theme
  • The middle window is a new, updated Wilma theme
  • The right window is Tenderfoot theme (just for comparison)

Video Example
https://youtu.be/9B0_cevrEeE

Reviewers' expertise

Candidates for reviewing this PR should have some of the following expertises:

  1. HTML, CSS, JavaScript

Copy link
Contributor

@chenejac chenejac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@milospp please check my comment

@@ -23,6 +23,7 @@ VIVO wilma theme: screen styles
@charset "UTF-8";

@import url("reset.css");
@import url("grid.css");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@milospp do we need this line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't, I forgot to remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done! Now it's reduced to a total of 5 file changes in PR

/* margin-top: var(--bs-gutter-y); */
}

.col-1 {
Copy link
Member

@litvinovg litvinovg Mar 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found only col-md5 used once and col-md7 used once. All other 'col-' classes aren't used, right?
The same is related to container-xxl, container-fluid, container-xl, container-lg, container-md, container-sm
If that is the case I would suggest to clean up not used styles.

@chenejac chenejac requested review from wwtamu and gneissone March 8, 2025 12:31
@gneissone
Copy link
Member

Screenshot 2025-03-20 at 15 43 25

Noticing a delay in the responsiveness on the home page. If I quickly decrease the window size there is a half second where the page looks like in the screenshot above. It might be related to the login box, since I'm not seeing it when logged in. Any idea what's going on?

@milospp
Copy link
Contributor Author

milospp commented Mar 22, 2025

Screenshot 2025-03-20 at 15 43 25

Noticing a delay in the responsiveness on the home page. If I quickly decrease the window size there is a half second where the page looks like in the screenshot above. It might be related to the login box, since I'm not seeing it when logged in. Any idea what's going on?

I just tested it in and I had no issue
Google Chrome (Version 134.0.6998.118 (Official Build) (arm64))
MacOS Sequoia 15.3.1

Also tested in Safari and Vivaldi browser

Screenshot

ScreenRecordResizeGif

Can anyone else confirm?
Also can you provide runtime.configuration, also have you tried it on the fresh instance?

@gneissone
Copy link
Member

Very strange.

Responsive.mov

I can't replicate in Firefox or within Chrome in incognito mode. I've tried turning off all my extensions still no change. Since it doesn't happen in incognito I assume it's an issue on my end rather than with the implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants