chrome

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 1.0% — this entity appeared in 27 of 2,852 analyzed posts/comments in the seven days ending that day (34 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-13 19:23 UTCComment

   Small correction on the zoom theory above -> Chrome stores page zoom per origin, not per path, so / and /index.html on the same host share one setting. Worth ruling out early instead of chasing. Separate from your rendering problem, but since you're serving robots.txt and a sitemap: I'd flip that redirect so /index.html goes to /, not / to /index.html. We run Hetneo's Links so this is the bit I always nag about -> a homepage canonicalised onto the file name turns into small duplicate-URL annoyances later. Won't fix the layout difference, still worth changing while you're in there.

2. 2026-10-13 11:23 UTCComment

   It turned out to be a brave browser bug with the zooming, once i set to 100% again and back to where i was, all pages look the same. I noticed it when chrome was working perfectly fine with no zoom.

3. 2026-10-13 09:24 UTCComment

   Ok so i messed about with zoom to see if that had anything to do with it since i dont use zoom on chrome, anyway brave issue is gone now......so it was zoom settings in brave.

4. 2026-10-13 09:19 UTCComment

   I think you are right, chrome is absolutely fine, its brave browser thats not scaling correctly

5. 2026-10-13 09:10 UTCComment

   Open DevTools on both URLs and compare the Network tab side by side. With hand-rolled static servers the usual cause is that one route serves the HTML fine but a CSS file or font fails, either because the stylesheet is linked with a relative path or because your helper sends it with the wrong Content-Type, so the browser ignores it. Also check that the response for / isn't going through a different branch of your code that returns slightly different HTML (missing the viewport meta tag, for example). If both responses and all assets look identical, try resetting zoom with Ctrl+0, since Chrome remembers zoom per URL path and that catches people out more often than you'd think.