Skip to content

eliminate horizontal scroll caused by footer #9669

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

Merged
merged 1 commit into from
Jan 9, 2020

Conversation

silverwind
Copy link
Member

fixes an issue with horizontal scroll on all pages on mobile, caused by the page footer being too wide for some reason.

Before (notice horizontal scrollbar)

After (no more horizontal scrollbar)

@zeripath zeripath added the topic/ui Change the appearance of the Gitea UI label Jan 9, 2020
@zeripath zeripath added this to the 1.12.0 milestone Jan 9, 2020
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jan 9, 2020
@codecov-io
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (master@a311ace). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #9669   +/-   ##
=========================================
  Coverage          ?   42.25%           
=========================================
  Files             ?      587           
  Lines             ?    77987           
  Branches          ?        0           
=========================================
  Hits              ?    32956           
  Misses            ?    40991           
  Partials          ?     4040

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a311ace...e3b96ea. Read the comment docs.

@@ -774,6 +774,7 @@ footer {
.container {
width: 100vw !important;
padding: 0 0.5rem;
max-width: calc(100vw - 1rem) !important;
Copy link
Member

Choose a reason for hiding this comment

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

Back to !important are we, isn't it? 🤣

Copy link
Member Author

@silverwind silverwind Jan 9, 2020

Choose a reason for hiding this comment

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

Yeah, it's needed because it is overriding this style from fomantic:

.ui.container {
    max-width: 100%;
}

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Jan 9, 2020
@zeripath
Copy link
Contributor

zeripath commented Jan 9, 2020

We really do need to move to less completely...

@zeripath zeripath merged commit b372211 into go-gitea:master Jan 9, 2020
@zeripath
Copy link
Contributor

zeripath commented Jan 9, 2020

Please send backport to v1.11

@lafriks lafriks added the backport/done All backports for this PR have been created label Jan 9, 2020
@silverwind
Copy link
Member Author

We really do need to move to less completely...

Not sure I follow. Personally, I'd rather move to Sass 😉

@zeripath
Copy link
Contributor

zeripath commented Jan 9, 2020

I meant build our CSS directly from fomantic less by integrating with its theming system etc. so we can drop those !important

@silverwind
Copy link
Member Author

Ah, yes. I don't think we actually need to integrate that tightly. Theoretically it's enough if our styles are loaded after the fomantic styles for them to win. Still, I prefer to "reinforce" statements via !important just to make sure they stick. I see !important as more maintainable than trying to keep up with changes on fomantic's side and there will always be a certain amount of styles that will need to be overwritten because fomantic is very opinionated.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/done All backports for this PR have been created lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/ui Change the appearance of the Gitea UI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants