- From: Frank Tobin <ftobin@neverending.org>
- Date: Fri, 11 Jan 2002 16:08:25 -0500 (EST)
- To: www-html@w3.org
Philip Brown, at 12:50 -0800 on 2002-01-11, wrote: > One could argue that it does not make sense for lynx and similar browsers > to implement CSS. However, they could still benefit from some kind of > pagebreak functionality. While many "user agents" choose not to implement > CSS, MOST of them have a "print" function. There are CSS properties that are designed for terminal-oriented browsers. Lynx and simlar could implement those. > The author could adjust colors, settings, fonts, you-name-it with CSS. > The viewer/user could adjust font sizes, print margins, etc. on that > end. But you will STILL WANT a pagebreak before the second H1 header, > otherwise, the printout will not be clearly executed. The author has the freedom to use !important declarations, and similarly, the user has the ability to override this. The user always gets the last word, in my book, on what presentation they choose to get, whether it be fonts, colors, or pagebreaks. You can't say for sure what the end user "STILL WANT"s. > To achive this functionality, I am proposing a specificly non-CSS > method, so that browsers that have no use for CSS, can still get > pagebreak information with a minimum of recoding. I'm glad you are at least aware of CSS, and it's purpose. But you *know* this isn't going to recommended. Printing is presentation, and should be in CSS. Basing your argument on the idea that there are browsers with no use for CSS is poor, since all end-user browsers can use CSS. -- Frank Tobin http://www.neverending.org/~ftobin/
Received on Friday, 11 January 2002 16:08:26 UTC