Session log — Safari wide margins on the homepage

← All session logs

Session log — Safari wide margins on the homepage

3 June 2026, evening · Medilearn · Hasmukh with Claude · auto-published from the local journal entry. A polished narrative version can be requested in any future Claude session.

Summary

Hasmukh noticed the live medilearn.africa homepage showing wide empty margins on the sides in Safari, while it looked fine in Chrome, and asked why. Investigated the site's styling end to end and found no fault in the website. The homepage is built as a centred column with a comfortable maximum width (about 1200 pixels), which is the same in every browser. The wide gaps in Safari are almost certainly down to the viewing conditions, not a bug: either Safari is zoomed out a little and remembering that for the site, or the Safari window is simply wider than the Chrome window. No changes were made to the site.

Decisions

  • Confirmed the report was about the live public site, medilearn.africa (the medistage build), and worked against that.
  • Did not change the global content width. The centred, capped width is a sensible design choice for readability on large screens, so it would only be changed if Hasmukh actually wants the content to fill more of the screen.
  • Gave Hasmukh the simplest first step, resetting Safari's zoom, before considering any design change.

Changes made

  • None. This was a diagnosis only.
  • Checked the homepage styling, the page structure, the plugin stylesheets that load site-wide, and confirmed there were no stray or injected rules causing the difference. The Past Events plugin styling (recently updated) is properly contained to its own page and does not affect the homepage.

Follow-ups

  • Resolved. Resetting the zoom in Safari (View menu, Actual Size) closed the gaps. Confirmed by Hasmukh as fixed. The site itself was never at fault.
  • If he would prefer the content to fill more of the screen in both browsers, that is an easy, deliberate change to make on request.
  • The browser inspection tool was not connected during this session, so the comparison was done by reading the site's styling rather than viewing it live. If needed next time, reconnect Chrome for a side-by-side look.