Ugh. The days of the browser-conditional pages should be long gone. What happens when a corporate proxy caches your page? How will it know which version to cache?
Please don't do browser-sniffing. Just write good HTML. If you want more control over the layout, use PDF.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply. | [reply] |
Well, for example, both Yahoo's and Microsoft's homepages do both client- and server-side browser sniffing, so we're a ways off from seeing the practice disappear.Also, for specialized design-intensive sites, you may want to do some tweaks... minor stuff, and if it's cached, then no big deal... just won't look quite as nice. And, of course, you can turn caching off for your page, add random values to URLs to get around poorly-built corporate caches that ignore the cache flags in the server response, etc. But, the main point is that, for artists/designers, there is still a need to be browser-specific for certain web projects where to-the-pixel control is needed. But, as I said in my post... the browser sniffinf was just an example. I really just want to know how to best handle publish-time conditionals in a general sense.
| [reply] |
| [reply] |