Re: problem with no javascript

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: problem with no javascript
by Jim Dabell on Monday 03/Mar/2003, @05:26

@import isn't a particularly bad hack, it's valid css. If your server is configured correctly, it's usually a matter of a few bytes the first time you access a site that uses it.

As for making sites compatible with older user-agents, you get this for free by writing valid, meaningful html, and hiding the css. As I said before, if you are relying on css, you are doing something wrong, it's optional for user-agents, there are plenty that will never support css. If you aren't relying on css support, there won't be a problem with older browsers. Okay, so I'm ignoring javascript, but the same argument applies to that as well.

I don't see what precludes alternate stylesheets with @import, unless there is a browser bug I don't know about that affects this combination. Most of my stylesheets get automatically shielded with @import by using a combination of mod_rewrite and a simple php script.

The biggest obstacle to xhtml support on the web is internet explorer, it still doesn't support it. ie6 will be in use for years to come, essentially blocking proper use of xhtml for that timeframe (xhtml as text/html is a hack that only works because no browser implements html properly).

Related Links

·   Articles on KDE Official News
·   Also by Jim Dabell
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"I switch between vi and xemacs quite a lot. I'm happy with both." -- Simon Hausmann
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.