Re: Uh yeah - so how do I compensate for it in the page?

Post #273,947 by ubernostrum 11/26/06 4:28:12 PM Reply	Re: Uh yeah - so how do I compensate for it in the page? CSS people have been compensating for bugs for years without doing UA sniffing ;) \r\n\r\n But this is largely a red herring; my point is simply that UA sniffing to determine what features you'll let the user see is, and ought to remain, dead. If it's the most efficient way to solve a CSS bug, then that's another story, but the question here is things like whether you send your CSS to the browser at all, not whether you send the fix for a 2-pixel rendering bug. --\r\nYou cooin' with my bird?
Post #273,953 by tuberculosis 11/26/06 4:55:33 PM Reply	I mostly agree but then there's that whole webtv thing again. [link\|http://www.blackbagops.net\|Black Bag Operations Log] [link\|http://www.objectiveclips.com\|Artificial Intelligence] [link\|http://www.badpage.info/seaside/html\|Scrutinizer]
Post #273,959 by ubernostrum 11/26/06 5:08:51 PM Reply	Re: I mostly agree WebTV needs to go on the garbage heap ;) \r\n\r\n There's a new incarnation of that idea being pushed at work, we had to basically set up completely segregated versions of our sites on subdomains with their own templating and whatnot to deal with it and send the users over there, because there's no way to detect it (thanks to the way it works, to a server it's indistinguishable from normal IE 6). --\r\nYou cooin' with my bird?
Post #273,992 by drewk 11/26/06 10:30:10 PM Reply	Couldn't you use your WAP page? I'm assuming anyone who cares about early adopters is writing pages for people surfing on their cell phones. I would guess the pages you server up to them would also work (sorta) on WebTV, wouldn't they? === Kip Hawley is still an idiot. === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]
Post #274,027 by ubernostrum 11/27/06 12:26:58 AM 11/27/06 12:32:12 AM Reply	Re: Couldn't you use your WAP page? Not really; the TV stuff, because of the interface it uses, had a different set of requirements for visual presentation. Which, fortunately, is really easy to do; one of my co-workers [link\|http://www.postneo.com/2006/07/26/acknowledging-the-mobile-web-with-django\|wrote up how we handle this sort of thing] for our mobile sites. \r\n\r\n Edit: I should probably also take this moment to pimp Matt's talk from PyCon on [link\|http://postneo.com/talks/pycon2006/\|mobile development with Python]. --\r\nYou cooin' with my bird? Edited by ubernostrum Nov. 27, 2006, 12:32:12 AM EST Expand All History
Post #274,033 by tuberculosis 11/27/06 1:34:21 AM Reply	Re: I mostly agree WebTV needs to go on the garbage heap ;) OK, there we completely agree. However, I believe there is a 'webtv' in the user agent string if you look for it. Failing that, you can do a screen size check in js and redirect them. [link\|http://www.blackbagops.net\|Black Bag Operations Log] [link\|http://www.objectiveclips.com\|Artificial Intelligence] [link\|http://www.badpage.info/seaside/html\|Scrutinizer]
Post #274,035 by ubernostrum 11/27/06 5:07:33 AM Reply	Re: I mostly agree Unfortunately, it's not actually WebTV, it's a WebTV-alike. I'll go poke at logs sometime this week, but I seem to recall that one of its major annoyances was not advertising itself in its UA string, and instead trying to be as much like IE6 as possible. --\r\nYou cooin' with my bird?

Welcome to IWETHEY!