........................................................................
Phillip_McCavityClaude gave me some browser settings to change but also included this note:
Would a style change prevent this? Yes — one line
This is a real weakness in the page, independent of your browser. Uncapped container-fluid
means the layout has no defence against any viewer's zoom or scaling being off.
For the site owner:
/* after bootstrap.min.css */
.container-fluid { max-width: 1800px; margin-inline: auto; }
max-width beats width: 100%, so it needs no !important — just later in the cascade. Below
the cap nothing changes; above it, content centers instead of stretching.
Worth pitching to Spanky on grounds better than this bug: line length. Text beyond ~90
characters per line is measurably harder to read, and a forum at 3998px is running 400+
character lines. The cap is good typography that happens to also make the site immune to
this failure mode. Swapping container-fluid → container would work too, but 1320px is
probably narrower than he wants.
........................................................................
SpankyThank you.
I will take a look.
What were your bad settings so I can reproduce it?
........................................................................
Phillip_McCavityHere is more of the answer. Note I haven't tried these things yet. There are a lot of things
going on and its not hard to scroll around the problem.
● Diagnosis is solid — and the surprising part is that this isn't really a campidiot
problem, even though it's the only site that looks wrong.
What's actually happening
The site ships a hidden debug widget that writes the live viewport width into the page.
Your saved copy captured it:
document.documentElement.clientWidth → 3998
Your browser is presenting a 3998 CSS-pixel viewport. A normal one is 1280–2560. That's
the fault, and it's browser-side, not site-side. It also explains your description
exactly: at that scale everything renders tiny, and the layout is ~2–3× wider than the
window can comfortably show.
Why only this site looks broken
The site's root wrapper is:
<div class="container-fluid min-vh-100 ...">
Bootstrap 5.2.3 defines .container-fluid as width: 100% with no max-width, and I checked
their stylesheets — nothing overrides it. So it fills whatever it's given, all 3998px of
it.
Compare Bootstrap's regular .container, which caps at 1140px / 1320px. Nearly every other
site on the web uses a capped container of some kind. At a 3998px viewport those sites
just center their content and look small — not broken. Campidiot stretches to fill it.
So the browser fault is global; this site is merely the one that reveals it. Worth
knowing, because "only one site is wrong" naturally sends you looking at that site.
Browser settings, in the order to try
1. Ctrl+0 on the page. Firefox persists page zoom per site, indefinitely, in
content-prefs.sqlite. One stray Ctrl+scroll sticks forever. This is the single most likely
cause of a sudden one-site change.
2. Settings → General → Zoom:
- Default zoom → 100%
- * Uncheck "Zoom text only." This one matches your symptom precisely — "when I increase
it, it now takes forever to scroll." With text-only zoom, Ctrl+= enlarges text but never
rescales the layout, so the page stays 3998px wide no matter how much you zoom. You can't
fix the width by zooming, which is exactly what you described.
3. about:config → layout.css.devPixelsPerPx — must be -1.0 (follow system). Any other
value overrides your display scaling globally. Right-click → Reset.
4. about:config → ui.textScaleFactor — should be 100.
5. OS side. You're on Fedora — GNOME Settings → Displays → Scale. If this changed, or you
attached a different monitor and GNOME applied a different scale, Firefox inherits it.
To pin down which layer is at fault, open the console (F12) on the site and read:
document.documentElement.clientWidth // want ~1200–2000, you have 3998
window.devicePixelRatio // combined OS scale × page zoom
window.screen.width // what the display reports
If Ctrl+0 fixes it, it was per-site zoom and you're done. If it doesn't, check whether
Firefox's own tab labels and menus look tiny too — if they do, it's global scale (steps
3–5), not the page. A quick isolation test: firefox --profile $(mktemp -d) renders with
factory prefs, which separates a profile/extension cause from an OS-scaling one.
........................................................................
SpankyI want the viewport fully expanded. Fuq centered viewports.
Maybe I should make it a preference?
That sounds ideal.
........................................................................
Previous | First | 1 | Last | Next