Stupid question about CSS or creating a main reference

  • Thread starter Thread starter D
  • Start date Start date
I feel like I am somewhere in the middle on this issue...I think CSS is
great for *some* things, fontfamilies, sizes, colors, link styles and
colors..and things along those lines. For trying to totally build a site
with only CSS though..it just leaves too many viewers unable to see the site
properly. Even if Netscape were to cease to exist tomorrow ( we can only
hope :-)...there's still too many people that will have it installed on
their systems for a number of years to come. My guess is as things evolve,
there will probably be something to take the place of CSS even before it is
universally accepted.

--
Joe

FrontPage Users Forums at:
http://www.timeforweb.com/frontpage/

Remove AA to reply with email
 
But you can use strictly css with no tables and still have NN work
properly.CSS isn't a panacea but it is a very good tool especially when
accessibility is important. A site should degrade gracefully when CSS is
used. If it doesn't then CSS wasn't used properly. For that matter, if you
have bad HTML NN 4.x will display a blank page. To condemn a whole web
standard CSS2 because some people don't use it properly isn't right. We've
all seen bad mark-up whether it is HTML or CSS.

CSS will be around as long if not longer than HTML Current web standard is
XHTML and CSS 2. Both XHTML 2 and CSS 3 are in draft mode right now with CSS
4 starting development.

One of the things I like best about using CSS2 for layout it that the pages
using it *DO* work on more devices. I hate checking web mail on my PocketPC
because I have to scroll every line and half of the buttons are hiddlen.
Why because it is a table based layout far too wide for my PocketPC screen.
Same page laid out with CSS would have the buttons and content wrap. Okay,
I'd have a longer vertical scroll but I wouldn't have a horizontal scroll
for every line I'm trying to read.

I'm not saying you shouldn't use tables. Even in a pure CSS-XHTML site there
maybe tables, data tables not layout tables.
 
XSL is for XML not XHTML or HTML, both of which will be around for at least
the foreseeable future.
 
First there are no standards, what we have is W3C recommendations,
government and organizational guidelines!

If there were standards, then whatever tags that are part of the
recommendations that we add to our pages would work in all browsers exactly
the same. Since the HTML 3.2 recommendations have been around the longer,
every one of the tags should work the same in all browsers, but they don't,
so there are no standards, as much as some would like to think.

As example, you purchase a telephone set from any manufacturer (made to work
in your country) and it will work when plug into any telephone jack (within
your country). That is a standard.

You purchase a PCI card from any manufacturer for your PC, it will fit into
any motherboard made by any manufacturer that has a PCI slot, that is a
standard.

Bottom-line every developer is free to choose whatever technology they want
to use, but non of those currently available is cure-all.

Also one need to consider the amount of time and effort it take get each
technology to work cross-browser, personally when it comes to page layout, I
can do it with tables faster then trying to position elements using pixels
that would look and function the same in any graphical browser a user may be
using.

I agree 100% with Joe Rohn, in the use of CSS1 for specify fonts related
attributes, etc. (Note: I prefer not use CSS1 for anything other than
modifying link styles.)

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
We'll just have to agree to disagree on this issue. For me it is much faster
to work in CSS than deal with nested tables. Apparently the opposite is true
for you.

FWIW, while the card will fit in the PCI slot it may not work in the
computer since that depends on whether there are drivers for the OS. That's
analogous to how HTML is implemented. The W3C tells what a piece of code is
supposed to do but leaves actual implementation to the browser manufacturer.
To me that is exactly the same as trying to use a software based PCI modem.
If you are running an OS that supports that modem it will work but if you
try to run it ona Linux system that doesn't have drivers you are out of
luck.
 
I will agree to disagree as far as which is faster to implement.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================
 
Back
Top