faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: problem with no javascript
by Shift on Monday 03/Mar/2003, @04:28
|
I now the @import tips but it is always a hack.
I consider that Netscape4.x is dead and that you can upgrade with other browsers following w3c standards very easily.
If we continue making site compatible with Netscape4.x and IE3.x then XHTML and CSS will stay a dream but I don't want that.
For me using @import is bad because I can't use alternate stylesheet with this :( |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
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).
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|