4 ms·
Nearly every selector used in that mockup either: 1. Flat-out doesn't work in Internet Explorer; or 2. Requires certain hacks to align Internet Explorer's rende
by rbritton 17y ago
Nearly every selector used in that mockup either: 1. Flat-out doesn't work in Internet Explorer; or 2. Requires certain hacks to align Internet Explorer's rendering with more compliant browsers. I can understand how it's much nicer to have a functional prototype, but I can't agree with it being worth the difference in the time invested.
Very, very few clients I've ever worked with use something other than Internet Explorer. It just doesn't happen, and I can't even count the times I've had to dumb down layouts because the requirements to overcome IE's limitations weren't worth the time investment.
- tptacek 17y agoYou may be missing the point. 100% of a mockup done in Photoshop won't render in IE. It's a mockup.
- rbritton 17y agoMy point is that building a prototype that won't render correctly in IE (i.e., the browser likely in use by the commissioning client) as it's described in that article is counter-productive. If the client can't see it as it's intended, what's the point? Building up the prototype to a point where it is universally compatible will have two end results: 1. The designer is building multiple functional pages and putting in all the labor required. 2. The designer is providing the client with a nearly fully-functional page/site prior to full payment being received.