Hello, On Aug 21 10:05 Manne Merak wrote (shortened):
Daniel Bauer wrote:
... many web programmers and older sites ... still use tables and fixed width, size and position declarations instead of a floating design that adapts to different screen or paper sizes. ... Yes but if the browser can render the page correctly on the screen canvas it should theoretically be able to render it correctly to a paper canvas (using some scaling factor).
Not always. Because there are no scroll bars on the paper canvas! On screen a too big element (a table or image or whatever) results a scroll bar and for the user it looks correct. But what should the browser do for a canvas without scroll bars? Should it scale down the too big element until it fits in the imageable area (which seems a reasonable default for an usual image) or should it split the too big element into pieces to keep its original size (which seems a reasonable default for a table to avoid too tiny fonts in the printout) or should it print only the table on a separated page in landscape orentation if the table fits in the imageable area in landscape orentation or whatever else even more sophisticated magic? Another interesting case: Assume there are (big) images which fit exactly in the imageable area of a printer and between each image there are two lines of text. One line is meant to be the header line of the image. The other line is meant to be the footer line of the image. Should the browser scale the images down so that header, image, and footer fit in the imageable area or should the browser keep the original image size and print the text on separated pages? Without hints in the HTML where a page break makes sense the browser cannot produce a good printout automatically. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org