[kw-pm] kw-pm Digest, Vol 111, Issue 1

Nick Dumas nick.dumas at gmail.com
Thu Oct 11 12:54:59 PDT 2012

One of the first problems is defining "a page"
Netbooks have 600 px minus a bunch for window decorations.
People with monitors rotated to portrait orientation get upwards of 1900px

Width is even worse, since it won't generally be the size of the
monitor minus a bit, just a random click-drag resize to people's

On top of that, fonts and even graphics can be scaled up and down
based on the zoom settings of the user's browser too.

If at all possible, relaxed and dynamic is the way to go on the web.
When perldoc.perl.org/ changed to a fixed width layout, I had to go
and monkeypatch it back to dynamic width with some CSS overrides.
Now it looks uglier than it did before the change, but it is once
again useful to me since I can read it on both my netbook (narrow) and
desktop (wide), side-by-side with code I'm working on (even narrower!)
or on a second monitor (extra wide)

 - Nick

> Not sure if anyone has had the need to do the following but I thought I'd throw it out there. I have data displaying on a webpage (dynamically generated) in a HTML table - 1 column for text, 1 for images (if there are any), and 1 for more text. I want to have it so that a row does not span 2 pages when printed (very much like what page-break-inside: avoid seems to accomplish). In some cases the first column's text can a few "lines" long or it could be 20 lines long, causing the row to expand vertically and therefore span 2 pages. Since the text (length, fonts, etc..,) and images (present or not, number of) vary it makes it hard to maximize the number of questions per page while staying within the constraints. If you know of a decent approach to take to get the desired paging results I'd like to hear them. Cheers.

More information about the kw-pm mailing list