|
Posted by Andy Dingley on 11/27/64 11:59
peteraward@gmail.com wrote:
> Except that I have used XHTML 1.1 elsewhere and been able to use CSS
> with it in the same way, same browser, and have it actually work.
Web authors regularly "use" a badly mangled hybrid of HTML 2 and MS
Orifice, and even that manages to "actually work".
The question is, is it _correct_. Of course it merely "works". For
some value of "works", on at least one machine, in one location. If we
hope to make it work worldwide, on a good range of browsers and similar
devices, and to keep working for the forseeable future, then we have to
do better than merely getting it to behave itself long enough to watch
it work just the once. We have to start thinking about objective
standards.
> And I didn't see my message appear within 5 minutes, so I assumed that
> Google Groups had got an error in it's coding somewhere,
Thankyou for that. So why did you multi-post to different ngs too?
> But it does work when no standard decleration is used.
What's a "standard decleration" ?
CSS works with XHTML. Now I know _you're_ infallible (you can even tell
when Google is broken, knowing that you need to re-post your wisdom to
it), but have you not considered for a moment the idea that this stuff
_works_, and that if it didn't, it would have been fixed? Guess what -
_you_ are doing something wrong.
Go and learn how to use XHTML.
Go and learn how to use XHTML on the web (this is currently different)
Go and learn why XHTML 1.1 doesn't work for the web.
If you do all this, and the web is stil broken for you (after all, it
couldn't be your fault), then when you come back remember to post a URL
to the site because we can't diagnose this sort of complex issue from a
short fragment alone.
Don't forget to multi-post your replies too, just in case you catch
Google stop working again.
Navigation:
[Reply to this message]
|