I've been swept up in the recent happenings of Rocketboom and the leaving of Amanda Congdon from the popular vlog. In a recent post on her blog, Amanda talks about giving an interview on the MSNBC show "Scarborough Country". So I went out the the Scarborough Country website to see if the interview was up on the web. While the Congdon video was not yet up on the site, I was attracted to another story. When I clicked the link to view the video, I encountered a page that told me, "To use this product, you need to install free software."
If you haven't guessed yet, I'm browsing via Firefox and apparently http://video.msn.com doesn't much care for Firefox. It probably has something to do with the fact that Firefox doesn't support ActiveX usage. My question though is who cares? If you're a national news outlet (or in the case of MSNBC, desperately hoping someday the public views you as such), how can you ignore non-IE users? I'll admit, when I first started in web development, I had the luxury of ignoring non-IE browsers due to our applications being intranet applications and we could issue such a requirement. Nowadays though, to not support Firefox or Opera, would probably mean I'd soon be looking for a new job. There are too many users out there not using IE. It used to be a throwaway amount, it's not anymore. A recent article pins US Firefox usage above 15%. In Germany over 39%. Australia, 24%. The article points out that in the united states, IE usage has dropped below 80% and worldwide it hovers at around 83%. Worst case, MSNBC and sites that adopt it's exclusionary topic, are ignoring 20% of the worlds populus. Best case, they're ignoring only 17%. That still (with rounding ) is 1 in 5. If 1 in 5 people come to your site and it doesn't work for them, then you may need to rethink your goals and are you accomplishing them. In the case of MSNBC and their attempt to bring me news, I would say they failed, since I did not open IE and load up their site once I encountered their friendly error page
P.S. I loaded up, Foxnews, CNN, ABC News, and CBS News, all of which worked fine. Not suprisingly, NBCNews.com redirects to MSNBC
I need your help!
I have a page that I'm trying to cache. This particular page is a details page for a tournament website. The tournaments run over several days. To handle the user load on the website, I'm working to implement output caching. Easy enough right? Just slap a <%@ OutputCache %> directive on the top of each user control and voila!.. done right? WRONG!
For some reason one control is simply giving me the fits. This particular control displays the schedule for a particular day. The day is selected from a drop down list which is on the user control. The AutoPostBack property is set to true. On postback the control simply does a Response.Redirect back to the details page, putting the requested day (from the dropdownlist) into the querystring so that there are two variables in the querystring, ID and day. Coincidentally enough that is what I have for my VaryByParam property, VaryByParam="ID;day". This seems to work...sometimes...and other times it doesn't. I can make it fail nearly 100% of the time if I load a particular page and then reload it using ctrl + F5. When I do a reload using ctrl + F5, any ensuing change of the dropdownlist produces a javascript "__doPostBack is not defined" error. When viewing the source, the Viewstate for the whole page is a fraction of what it was when the page was working and more importantly the __doPostBack function does not exist at all in the page anymore.
If I don't ctrl + F5 everything seems to work (I say sometimes, because at seemingly random intervals, I will get the same error). As soon as I ctrl + F5, I get the javascript error when I change the dropdownlistvalue. I don't get it. If in fact the control is cached, I should get everything back from the server including the viewstate. So what am I missing? Ideas?