This is very strange. However, I can't get the overflow: auto; and, more specifically, overflow-x: auto; behaviors to work properly on any of the Mozilla browsers (Firefox, Camino) on an Intel mac and yet they work fine on a PPC mac and in Windows. Regardless of whether scrollbars are needed or not, they always crop off the right 50 pixels or so of all text - even midword. Ideas anyone? I am assuming that this is just a bug in the newly Intel-compiled mac software.

Dani AI

Generated

reported that text inside a scrolled container on Intel Macs using Mozilla builds is being clipped by roughly 50 pixels on the right (PPC Macs and Windows unaffected). That symptom usually points to a layout/measurement interaction rather than plain HTML content — either the browser is miscalculating the available content width, or a child element/box model rule is forcing overflow in an unexpected way.

Troubleshooting checklist (isolate before guessing it's a platform bug):

  • Reproduce with a minimal HTML/CSS test case (one container and plain text) so other styles/scripts are out of the picture.
  • Toggle document mode/doctype (standards vs quirks) and compare results.
  • Inspect computed sizes (offsetWidth/clientWidth) for the scroller and its first child; look for fixed-width children, floats or nowrap long inline elements.
  • Test different fonts/font-sizes — subpixel rounding can shift wrap points.
  • Try the same page in Firefox safe mode (extensions off) and in another Gecko build or Safari to narrow whether it’s Gecko-on-Intel specific.

Practical workarounds that often hide the clipping without changing layout logic:

  • Add a small right padding inside the scrollable element so text never reaches the clipped edge.
  • Force the inner box to include padding in its declared width using the vendor box-sizing flag so the right padding doesn't expand the scroll area.

Example CSS (adjust padding to taste):

.scroller-inner {
  padding-right: 24px;
  -moz-box-sizing: border-box;
  width: 100%;
}

Use these fixes as stopgaps. If the minimal test still clips on an Intel Mac build, gather a concise reproducible case (HTML/CSS, exact OS build, Firefox/Camino version, steps) and file it with Mozilla so it can be tracked. ’s point is valid — this is one more OS/browser combination to include in cross-testing.

Very ugly! Great, one more OS/Browser combo to add to the mix when coding sites.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.