W3C home > Mailing lists > Public > www-style@w3.org > November 1997

Re: Header, Footer, and Sidebars

From: Hakon Lie <howcome@w3.org>
Date: Sun, 30 Nov 1997 11:24:42 +0100 (MET)
Message-Id: <199711301024.LAA29517@stovner.a.sol.no>
To: Todd Fahrner <fahrner@pobox.com>
Cc: www-style@w3.org
Todd Fahrner writes:

 > " I thought it was established that the UA has
 > " a hypothetical default stylesheet and that changing the default font in the
 > " UA changes the base font size in that stylesheet. Therefore, changing the
 > " font on the toolbar should change the font size in any element for which
 > " font size has not been specified either in absolute units or relative to an
 > " ancestor element specified in absolute units. Conversely, elements declared
 > " in author stylesheets in absolute units should be unaffected by UA font size
 > " changes.
 > 
 > This is precisely as I see it, also. Thanks for the nice
 > articulation, David. What I'd really like to know is whether there's
 > any dissent on this point (especially among implementors).

There is no disagreement on the goal, I believe. However, inserting
the base font size into the default style sheet is not always powerful
enough -- any 'font-size' setting (relative or absolute) on the same
element in a user/author style sheet will override it due to the
cascading rules. To strengthen the base font size, it should also be
used as the initial value of the 'font-size' property and the spec
should state that relative values on the root element are relative to
the initial value.

This way, the base font size would also apply to documents within
OBJECT elements.

Regards,

-h&kon

H      k   o   n      W   i   u   m       L   i   e
howcome@w3.org      http://www.w3.org/people/howcome
World     W      i     d     e       Web  Consortium









Todd Fahrner writes:
 > David Perrell wrote:
 > 
 > " I thought it was established that the UA has
 > " a hypothetical default stylesheet and that changing the default font in the
 > " UA changes the base font size in that stylesheet. Therefore, changing the
 > " font on the toolbar should change the font size in any element for which
 > " font size has not been specified either in absolute units or relative to an
 > " ancestor element specified in absolute units. Conversely, elements declared
 > " in author stylesheets in absolute units should be unaffected by UA font size
 > " changes.
 > 
 > This is precisely as I see it, also. Thanks for the nice articulation, David. What I'd really like to know is whether there's any dissent on this point (especially among implementors).
 > 
 > " It seems to me that constructing documents with includes is best done with
 > " files that are not stand-alone HTML. Why not reset the style state ONLY if
 > " the included file is a stand-alone HTML document? E.g., save/reinitialize
 > " style rules for each nested <HTML> element?
 > 
 > What if includes could reference elements within HTML files by [unique element or assigned] name, class, or ID, and that only the referenced element(s) and children would render? The default could be the HTML element (in which case the referenced doc's stylesheet would apply), or alternatively the BODY (in which case the referencing document's stylesheet would apply), a DIV, a table, paragraph, etc.  
 > 
 > ----
 > 
 > I've had some trouble with email lately, so this suggestion comes late, but this thread's participants should definitely check out "Frame-based layout via Style Sheets" http://www.w3.org/TR/NOTE-layout , dated about six months before the first CSS-P proposal. I've always wished this approach had found greater favor with implementors.
 > 
 > 
 > Todd Fahrner
 > mailto:fahrner@pobox.com
 > http://www.verso.com/agitprop/
 > 
 > The printed page transcends space and time. The printed page, the infinitude of books, must be transcended. THE ELECTRO-LIBRARY.
 > 	- El Lissitzky, 1923
 > 
 > 
 > 
Received on Sunday, 30 November 1997 05:25:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:53:53 GMT