Cliff Pruitt wrote: "Do you take a step backwards in your interface & force yourself not to use a specific design just cause the "standards" say it can't be done?"
I just went through this exact issue a week ago. I was coding a template for a weekly HTML e-mail for a client of mine who competes with iPod and iTunes. They wanted the layout to hold up in Web-based apps, desktop e-mail clients, Web browsers, and wireless devices. Now, I'm a big proponent of standards. But I knew when I accepted the project that standard HTML/CSS on their own would not create one more-or-less consistent layout across the variety of environments my client listed. The worrying started when I took a look at the iTunes e-mails. The layout was consistent across the board, regardless of what device or app I used. How? Tables. In the end, I coded the template in XHTML 1.0 Strict and CSS. After asking my client for information about its customers' browsers, devices, and physical abilities, and getting virtually nothing back, the right choice was standards. The layout may not hold up in every environment, but because my client couldn't give me any idea of the people who would eventually receive the e-mail, I had to make the template as accessible as possible. And I couldn't do that without standards. Nick _______________________________________ Nicholas S. Turner Gardner Loop Photography & Design, Inc. 4196 Merchant Plaza #339 Woodbridge, VA 22192 http://www.gardnerloop.com/ p: (703) 842-4897 f: (703) 991-2526 e: [EMAIL PROTECTED] ______________________________________________________________________ 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/
