--- Gunlaug Sørtun <[EMAIL PROTECTED]> wrote:
> 3: You clearly can't, or won't, test beyond fairly limited
> window-dimensions and conditions, so it's of no use to point out
> avoidable design-weaknesses. They will end up at the user-end no
> matter what.
> 
> The solution is to either live with an "only works as expected in
> some versions of IE" design, add some styling and make it work 
> "somewhat" in most browsers, or to re-think and re-do the entire
> layout in accordance with standards and make it work "more or less"
> everywhere.

Yes, I remember the painful decision to step away from standards
everywhere with this client. It's a kludge at this point. I agree. 

This layout is definitely killing some end user experiences.
Client-insistence is strong in favor for the too dark, line reading
width too long.  Only IE 6 and above, if that. No screen readers...
100% fluid width not consistent. 

No 800px, not even 1024! I butchered a full working standards-template
to get it to this current beauty.

Yes IE jumps... Barely getting just FF & IE addressed. Statistics show
50-50% these 2, with 1% other browser use likely generated from
testing, 1% IE 5 not past 2001.

Definitely at the "work somewhat" stage.

I've now decided to do a major pruning and just go back to a
only-for-FF story board with header-footer, otherwise empty
body/wrapper. I'll post if success. Yes weird on the earlier <del>
comment, it was a early AM hack for IE, it has to go anyway for even a
minimal degrade to work at this point.

______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to