Lazycoder

25Aug/041

Browing msdn with FireFox

Scott on Writing

Scott Mitchell still has problems with browsing MSDN using Firefox. I pointed to his first article on the problem. He re-presents his solution to the problem for use on MSDN. As of 12:37 PST on August 25, 2004 MS has applied a patch CSS to the MSDN articles. So now the code isn’t squished together. Yay!

Except they haven’t applied the patch to the MSDN library. :(

Well, that’s a lot of content to go check and apply the patch to and then regression test to make sure it doesn’t break in other browsers. But I found a work around!:)

First download their patch stylesheet from here or make your own.


PRE
{
	background:#EEEEEE;
	margin-top:1em; margin-bottom:1em; margin-left:0px;
	padding:5pt;
	white-space:pre;
	word-wrap:break-word;
}

Now there are two paths you can take.
1) create a custom stylesheet for FireFox to use following the instructions here. The downside to this is that it applies this new style to ALL websites you view and this style MIGHT break some of them.

2) Install the Web Developers Extension for FireFox (the official page for it is here) and use it’s “Apply CSS to this page” feature to selectively apply their patch CSS to the MSDN library pages that need it.

You can also create your own CSS patches for any other web pages that are broken in FireFox. :)

  • Pingback: JonGalloway.ToString()

  • Lowell Meyer

    Just wanted to quick add here that we have fixed this issue in the MSDN Library. Scott’s fix certainly would have solved the problem of code sample formatting– but that was actually intentional in non-IE browsers. Unfortunately, many of our internal content providers don’t keep the length of the lines of code in their samples very short… and so the new problem would have been pages that would have had rediculously wide widths. Once the code sample gets that wide, the rest of the page is pushed out.

    We decided that was an even worse problem.

    Anyhow, enough browsers support ways to allow

     text to word-wrap when necessary that we have been able to change our CSS so that code samples look good for everyone now, inside the library and out.  We're still checking around to ensure that we didn't miss anything (we have a ton of pages and content to verify), but for now we think all the code samples are fixed.  If you see otherwise, please let me know!
  • Pingback: msdn - StartTags.com