That's interesting... I've never noticed that App_Browser was named as such where it should be App_Browsers.  Huh.

I've briefly seen some other threads as well regarding the DNNNav provider but honestly haven't had much time to dig too deep.  In the end I'm in no hurry to upgrade to the 5.0 set so I'm not immediately affected but it would be nice to identify and rectify the problem before the time comes.  Actually probably won't be a problem at that time either because we're planning on using (currently using) the Telerik and Snapsis menu providers anyway.  I just don't want to run into other problems with IE6 if it is something unrelated to the DNNNav or something that combines with it to create the full problem.

I'd love to just get everybody on IE7+ in the company but the IT guys have their standards and don't like changing them very often -- seems that there are some apps that actually need us to be on the lower version.

Thanks for the observation though.  I may dink around a little more and see if I turn up something.

I can also verify under DNN5, using IE6 as a web browser, the navigation components of DNN are completely broken and turns your dynamic website into a single static non-navigatable page. Seems like any button that does a postback is broken in IE6. This should be a major show stopping issue, unless we don't care about the millions of people using IE6.

Anyone figure out a good fix for this yet?

I also verified it works perfectly under DNN5rc2 in IE6, but not in the final fully tested released build.

Alex, thanks for posting that up.  I agree with your viewpoint, I'd also love to see IE6 gone and replaced with the newer versions.  Slowly getting there.