Skip to content

fix(docs): make footer sticky and layout responsive on mobile - #63

Open
igorgbr wants to merge 1 commit into
ArjunSharda:mainfrom
igorgbr:fix/mobile-sticky-footer
Open

fix(docs): make footer sticky and layout responsive on mobile#63
igorgbr wants to merge 1 commit into
ArjunSharda:mainfrom
igorgbr:fix/mobile-sticky-footer

Conversation

@igorgbr

@igorgbr igorgbr commented Jul 29, 2026

Copy link
Copy Markdown

Closes #41

Problem: the footer used position: absolute; bottom: 0; height: 15vh, so it left the document flow and overlapped page content, and the fixed 15vh clipped its own contents on short viewports. In credits.html the <footer> was nested four levels deep inside Bootstrap .row containers, and in utcsecondstodatetime.html it sat outside <body> altogether (the <body> tag was opened inside <head>) — so it could not be positioned by CSS at all. Fixed-width inputs (size="30") inside .p-5 containers also caused horizontal scrolling below ~400px.

Fix: applied the flex sticky-footer pattern already used in lookuptimezonetime.html (body as a flex column with min-height: 100vh, footer { margin-top: auto }) to cdits.css, dttu.css, tcl.css, ustdt.css and legal/brandingcss.css; moved <footer> to be the last child of <body> in the two broken pages and fixed their duplicated <html> tags and stray </div>s; added max-width: 100% to the inputs. No new dependencies, JS untouched.

Tested at 320px / 375px / 768px and desktop, on every page.

image image image image

Replace the absolutely positioned footer with the flex sticky-footer
pattern already used in lookuptimezonetime.html. In credits.html and
utcsecondstodatetime.html the footer also had to be moved to be a direct
child of <body> - it was nested inside Bootstrap .row containers (and
outside <body> entirely in the latter), so no CSS could position it.
Cap input width so pages no longer scroll horizontally on small screens.

Closes ArjunSharda#41
@igorgbr
igorgbr requested a review from ArjunSharda as a code owner July 29, 2026 00:03
@igorgbr

igorgbr commented Jul 29, 2026

Copy link
Copy Markdown
Author

Thanks @ArjunSharda PR is up. It needs your approval to run the workflows — dependency-review is marked required and is waiting on that. Note the TimeConv Welcomer check fails in ~5s on actions/first-interaction@v3, unrelated to these changes; happy to open a separate PR for it if you'd like.

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.

Website does not show up correctly horizontally on mobile

1 participant