-
Notifications
You must be signed in to change notification settings - Fork 3
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
Responsive UI and front page #39
Comments
Course of action:
|
So what is happening is that the skeleton still has the old breakpoint in the javascript somewhere, but they do no longer correspond to the breakpoint in the css. Note that the skeleton still switches between modes: It does so at the OLD breakpoints, modified in fcf7b9e: |
☝️ that might explain the awkward scrolling behavior of the main pages as that is handled by javascript. |
I suspect that this was the motivation behind the change in the style sheet. For things to keep working it is better to keep the skeleton boundaries. E.g.:
|
But we still have to drop one (on or more) top-level item(s) from the main menu. |
Some old notes: Slack conversation leading to this issue: History for That resembles the change Peter refers to and it is currently live. Maybe there have been other changes too to other files too? Let's check that out.
On January 31st I made some changes to main.css.scss, could they have resulted in different behaviors? 9489f63 and 626ab9c On Feb 4th I removed several scss files with commit b603acb. Could that be a problem? Let's also check the history of the main page ... defintively things going on there too. |
With #41 it is better, but we still have responsiveness issues ont the front page.
The real problem is that we try to jam too much content on the front page.
This leads to scrolling issues and a less responsive frontpage.
Better would be:
But that is for some other time.
The text was updated successfully, but these errors were encountered: