== An actual use for the CSS overflow property I have written grumpy things about the limitations of the CSS _overflow_ property [[a long time ago CSSIrritation]], but I've recently realized that it does have one actual use in an environment such as WanderingThoughts. And that is to deal with a problem I periodically have with comments. The problem with comments on WanderingThoughts is that they can break the overall page layout. WT uses a table based layout, so an overly-long line in a comment forces the entire surrounding box to widen to contain it. The result creates a table with a huge width, causing the entry (and other comments) to also be absurdly wide and thus unreadable. (I usually fix these page width busting comments with magic site admin powers.) This is exactly the situation where CSS's _overflow: scroll_ is the right answer (instead of the wrong one). The normal drawback of this setting is that it destroys readability, but here it is better to destroy the readability of a particular comment than to let it destroy the readability of all of the text, and the comment formatting isn't something that I control. This is a pretty unusual situation, although I suppose that it applies to anything with user-contributed content in constrained layouts. (When you are writing main article text, the readability of your _overflow: scroll_ content is presumably important for the text's overall readability (otherwise, why is the content there at all?), *and* you control the content so you can reformat it in ways that don't destroy your layout while still leaving it readable. And you should, for obvious reasons.) PS: now that it is no longer 2006 ([[cf https://developer.mozilla.org/en/CSS/white-space]]) I could solve much but not all of this problem by [[finally fixing my usual issue with _
_ PreProblem]]. That still leaves _lynx_ sort of [[out in the cold
CSSLimitationsI]] but increasingly I could live with that (especially
just for comments).