For the past several years, I have been reading my news for MSNBC. I have liked their layout, their journalistic style, and their partisan slide to the stories that they run. But lately, I have become disappointed with them. I have recently switched from M$ IE to Mozilla Firefox as my primary browser on both my linux box and my desktop at work. It seems that either Firefox has trouble loading the MSNBC website, or there is something different about the site (that they do intentionally) that hinders the proper rendering of their site. There are times when I can't even view the website at all while using Firefox, but if I switch to IE, it comes up fine.
I have not taken the time to do any research, and this is all merely speculation, but the fact of the matter is that I have trouble viewing their site using a non M$ product. Anyone else experience the same issues?
Posted by doug at March 18, 2004 11:57 AMAt first glance, it works fine for me with Firefox. I just went to the page and clicked on one of the stories and both worked alright.
I read my news at abcnews.com.
Posted by: stacey at March 18, 2004 05:58 PMget back to slashdot where you belong! :)
Posted by: john at March 19, 2004 09:08 AMwow...it's all f-ed up for me. many of the nav images are pushed to the bottom and it keeps resizing the left navbar when i mouse-over it. neat. it's like a video game.
Posted by: john at March 19, 2004 09:11 AMIt now seems to be working fine for me. Who knows.. But a search of the Mozilla forumns yeilds a bunch of other complaints about similar happenings on any site that M$ runs, including hotmail. Who knows.
Posted by: doug at March 19, 2004 10:58 AMit's the code that frontpage or visualstudio produces. at work, some of our windows programmers through together a site and it had some issues.
one text section was set to be 4% wide, and then the title for that section was set to be 1222% wide so i would actually display properly. ;)
Posted by: john at March 21, 2004 02:30 PMOn a different yet related subject, I have a weird issue that seems to be Firefox related. Say I'm reading through my list of blogs. I go to one, read it, hit the back button and get a message about "/" being not found. It's so sporadic that I can't even make it happen again to get the entire error, even though it just happened a minute ago.
I have been able to get around this on pesky sites that I link to by linking to the /blog/index.[html|php] file directly instead of just /blog. But if it's a link I follow from someone else's site, there's no getting around it. Does anyone else know what I am talking about??
Posted by: stacey at March 22, 2004 10:28 AMThat may be a proxy issue, although, it should then happen every time. I notice that here at work if we don't set up the Apache proxy properly, you have to be very careful about whether or not you put the trailing slash on a URL. I'm not sure what's going on there though.
Posted by: doug at March 22, 2004 11:44 AMWe don't have a proxy, so try again. :) Happens at home too, not just at work.
Posted by: stacey at March 22, 2004 02:24 PMNot you.. :) The server that you are connecting to may have a proxy infront of it.. :) I have PREP/APRA set up that way...
Posted by: doug at March 22, 2004 02:28 PMI have the same problem with FireFox and MSNBC. Once in a great while, the page loads, but most of the time, the page does not come up at all. Funny how all non Microsoft dominated sites seem to work perfectly fine with FireFox, but any webpage infested with the "Microsoft Virus" (as I like to call any product or service dominated by them) never seem to work right, or not at all. It's one of the many underhanded ways M$ is keeping their monopoly on the Internet. I find it ironic that to protect the world from trojans, worms, etc, you need to use Internet Explorer for Windoz Update to work, yet IE and Windowz is responsible for 99% of the trouble out there.
I'll stick with www.cbsnews.com
Posted by: Jim at January 29, 2005 03:29 PM