> Would you please do some clean-up in there before further trouble-shooting?
That would sure be nice, wouldn't it? :) Unfortunately this is the mess
asp.net makes of the pages and I'm stuck with it. I'm afraid HTML Tidy won't
help me much as the pages are generated through asp. Going through some of the
w3c validation errors, though, I can put all of them in one of two categories.
---------------------------
Category 1: I did it right.
---------------------------
Take the first link to a style sheet. This is the markup I have in my code:
<link type="text/css" rel="stylesheet" href="includes/default.css"/>
And this is what it is after asp.net gets through with it (location changed so
I could put it on a live web site):
<link type="text/css" rel="stylesheet" href="details_files/default.css">
Notice it no longer has an ending tag "/>", and afaik there's nothing I can do
about it.
---------------------------
Category 2: I didn't do it.
---------------------------
All those errors about the <input> and <img> tags not having a close? Nothing
I can do about that either. I don't even put those input tags in there to
begin with. Asp does.
> FF, IE6 and Opera rendered the live page differently, so I made a copy.
> HTMLTidy protested wildly, and changed things. Leaving the DTD intact,
> but only after having added the missing XHTML pieces.
Fixing the errors in the .html page won't do anything except give someone more
experience with fixing errors. :(
> Now all browsers render the same, but it doesn't look like what any of
> them rendered before. Completely FUBAR.
Opera 8 and IE6 display the cart underneath the content, and FF displays the
cart right next to the content for me. I would like to see the fubar rendering
you're getting. :)
> Also, if the main content-container shall react on the presence/absence
> of that float, then the float should come first (as in your previous
> example). Of course it can be done backwards if you have a really good
> reason for it, but rather not.
If having the cart first in the source order won't make the pages more tedious
for screen readers or disabled-CSS people, I don't have a big problem with
moving it back up. However, if one of these people is browsing around the site
with something in their cart, they'll have to skip over the cart quite often.
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/