On Wed, Aug 4, 2010 at 6:36 AM, Zoran Zorkic <zo...@gmx.net> wrote: > > Yup, floating the img left did it. Thank you very much! > I really love how a thing like this comes up and just block the progress. > This was a interface for the app and I could not continue with fixing this > first :( > I did try asking a friend who is a lead developer at a web-dev company, but > he just said I should stick to tabels if I run into CSS implementation > problems. At times like this I wonder if he's right. I mean, his clients are > not complaining, not do they care how a site is built, as long as it looks > and works as it's supposed. His company does use a weird mix of CSS, HTML5, > AJAX and tables. > > In my honest opinion, tables should only be used where they, semantically, make sense. I've used tables to control the display of forms just for the styling, but thats a challenge to do in any other way. Pages should be written in semantic HTML, then styled with CSS after the page is written, adding a few divs here and there for styling purposes. Writing pages this way will keep the content separate from the design to search engines and screen readers. If theres a challenge to do something in CSS, just email a list like this and get several opinions. There's no excuse for using table layouts anymore with how far everything's come in ways of web standards.
Alex Mitchell http://gumware.com/ (in the process of a redesign) ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/