-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Bugfix/footer #8537
Bugfix/footer #8537
Conversation
Thanks for opening this pull request! This space is protected by our Code of Conduct - and we're here to help. |
Codecov Report
@@ Coverage Diff @@
## main #8537 +/- ##
=======================================
Coverage 81.91% 81.91%
=======================================
Files 101 101
Lines 5894 5896 +2
=======================================
+ Hits 4828 4830 +2
Misses 1066 1066
|
Code Climate has analyzed commit 9729e93 and detected 0 issues on this pull request. View more on Code Climate. |
@@ -528,6 +540,12 @@ a.btn-outline-secondary .fa { | |||
color: #6c757d; | |||
} | |||
|
|||
.container{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I'm a little worried about modifying default Bootstrap styles here, and about modifying the HTML and body styles... Is there a more minimal way to do this, or is this the only way?
Would it work to just absolute position the footer? And, I guess, add corresponding amount of bottom-padding to the body so it doesn't overlap anything?
Thanks for working through this with us, just trying to be sure it works on a variety of screen sizes and is maintainable and Bootstrap compatible! Thanks a lot!
What do you think, @avats-dev of my questions above? Thanks both of you!!! |
As far as I know, you will need to modify body container along with footer div for achieving this. Setting it absolute has a drawback that if there is more content, even then footer will be stuck at bottom. So, it's best to attach it to page container instead of viewport. You can see this for reference. We can also use flex, but that will also require editing body div. |
@avats-dev Sir, should i work on doing a better code? |
Hi, well, hmm -- in testing this in GitPod, i see some other layout issues resulting - like, here on tag pages: (compare to https://publiclab.org/tag/outreachy) However, other pages seem OK! Even in mobile-friendly page-widths: However, I see as @avats-dev mentioned, this doesn't happen much because our footer is quite full of content now. Balancing all of this, I guess I think we'd better leave the layout more standard and not make these changes, given that any customization will make our layouts slightly more brittle and harder to maintain. I want to apologize to @Asu1996 who put good work into this and solved the stated issue, and will make a new issue for @Asu1996 to make up for this, hopefully. Thanks, everyone, for your help on this, and my apologies for the reversal. I appreciate your patience! |
Fixes #5059 (<=== Add issue number here)
Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
rake test
@publiclab/reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Thanks!