- From: Eric A. Meyer <emeyer@sr71.lit.cwru.edu>
- Date: Thu, 7 May 1998 10:05:26 -0400 (EDT)
- To: www-html@w3.org
>> The reason I said it isn't quite that easy is that the browsers which I >>marked "YES" only support some of CSS, and none of them yet support enough of >>positioning to truly replace frames. For further information on the state of >>support for CSS1 (positioning is part of CSS2), see the charts at >>http://style.webreview.com/ > >However, lack of support for CSS in all browsers shouldn't be a reason not >to use it when authoring. Agreed. >Proper HTML documents will display OK also for older browsers. Thus, if you >are satisfied with that your design mostly will benefit those with the most >recent browsers, you can author with CSS and still know that the documents >are accessible for others. Yes. This is the main reason I'm so interested in CSS. However, most authors want to know that the appearance they worked so hard to create is going to display exactly the same in all browsers. We know this isn't possible, even at the HTML level, unless one goes to an all-graphic interface... but let's face it, that's what the people want. Also remember that there are CSS properties which, if used, will make the content unreadable in some CSS-semi-aware browsers. 'line-height' springs to mind immediately, but there are others. So, unfortunately, you can't KNOW that your documents will be readable by everyone, even if you're using CSS, unless you're careful to avoid historically buggy properties. </EMeyer> -- Eric A. Meyer - eam3@po.cwru.edu - http://www.cwru.edu/home/eam3.html Editor, WebReview's Style Sheets Reference Guide http://style.webreview.com/
Received on Tuesday, 26 May 1998 04:26:57 UTC