Ask a questionAsk a question
 

QuestionReport viewer and Internet Explorer 8

  • Saturday, April 04, 2009 7:28 PMInforMed Direct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I've just updated to Internet Explorer 8 and my web app reports don't render correctly anymore. They are fine in compatability mode. The reports use the Microsoft ASP.NET v2/VS 2005 report viewer. It's a shame as the rest of the site works fine. Anyone know if there's an update to the report viewer in the pipeline?

    BTW - I've just tried adding <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> in the <head> section of the report viewer page and it doesn't seem to work. Still renders in IE8 mode unless I change the entire site to compatability mode.

    Cheers, Rob.

All Replies

  • Monday, April 06, 2009 8:13 PMBrad SyputaMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Rob,

    You can use the DOCTYPE for Quirks mode on your page. See this article for more details http://www.communitymx.com/content/article.cfm?cid=85fee


    Brad Syputa, Microsoft Reporting Services This posting is provided "AS IS" with no warranties.
  • Friday, October 30, 2009 11:51 AMInforMed Direct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Anyone got any news on a fix for this to allow ReportViewer 2008 control to work with IE8 in native mode?

    Cheers, Rob.
  • Tuesday, November 10, 2009 5:49 PMDerekAtTempWorks Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I've taken to having the page run in compatibility mode as suggested above. It's a server side fix that works fairly transparantly to the end user.

    How you had any issues with protected mode blocking the print button ? errors like "could not load client print control" or  "An error occurred during this operation"
    -Derek @ TempWorks Software
  • Friday, November 13, 2009 2:28 PMInforMed Direct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I've taken to having the page run in compatibility mode as suggested above. It's a server side fix that works fairly transparantly to the end user.

    How you had any issues with protected mode blocking the print button ? errors like "could not load client print control" or  "An error occurred during this operation"
    -Derek @ TempWorks Software

    Yes, I'm stuck in compatability model and yes, I've had an issue with the print control. I raised a support call with WebHost4Life on it but to be honest, their reply is still in "to do" list.

    I hope Microsoft do release a service pack for this very useful component.

    Cheers, Rob.