none
Report viewer and Internet Explorer 8

    Question

  • 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.
    Saturday, April 04, 2009 7:28 PM

All replies

  • 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.
    Monday, April 06, 2009 8:13 PM
  • Anyone got any news on a fix for this to allow ReportViewer 2008 control to work with IE8 in native mode?

    Cheers, Rob.
    Friday, October 30, 2009 11:51 AM

  • 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
    Tuesday, November 10, 2009 5:49 PM

  • 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.
    Friday, November 13, 2009 2:28 PM
  • Same problem.

    If anyone knows a solution please inform me.
    This problem is really fucked up!

    Grt
    Monday, December 28, 2009 11:55 AM
  • The IE8 compatability of rendering is still not fixed AFAIK. The problem printing is a security issue in IE8 - a case where security has been improved and breaking older software. I sympathise with the developers here - you are caught between the a rock and a hard palce with security and backwards compatability.

    There appears to be two problems with printing. Something server side and something client side. The client side problem is that the control only works if the site is trusted so the fix is to add the website to the trusted zone.

    I'm not sure what the server side problem is. It works okay on my fully-patched Windows 2003 Server used for development but doesn't work on Webost4Life. I suspect there's a fix/patch needed on the server.

    Cheers, Rob.
    Thursday, December 31, 2009 12:17 PM
  • Remove the <doctype tag.

    Hopefully it helps!

    Let me know!

    Regards

    Thursday, December 31, 2009 12:30 PM
  • Removing the doc tag worked for me.

    Big thanks!
    Wednesday, March 03, 2010 12:01 AM
  • Hi there. Documentation for the new VS2010 control also contains information on switching between standards and quirks mode for the viewer control to work correctly. See
    Cephas Lin This posting is provided "AS IS" with no warranties.
    Wednesday, March 03, 2010 3:59 PM
    Moderator
  • Please reply with instructions on how you removed the <doctype tag.

    __________________________________________________________________
    William Vaughn
    Mentor, Consultant, Trainer, MVP
    http://betav.com
    http://betav.com/blog/billva
    http://www.hitchhikerguides.net

    “Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)”

    Please click the Mark as Answer button if a post solves your problem!

    Wednesday, March 03, 2010 6:07 PM
    Moderator
  • In my case, we use a master page, but our reports display in a ReportViewer on a separate aspx page without a master.

    I simply removed the entire

    <!

     

    DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

    from the top of the reporting page and the report we were having problems with rendered correctly.

    Wednesday, March 03, 2010 10:16 PM
  • You're welcome,

     

    Valentino

    Wednesday, March 03, 2010 10:33 PM
  • I assume that without this DOCTYPE line, IE8 is switching to a different rendering standard which is probably also what the meta tag does? Would still prefer a fix to the underlying reportviewer.

    Cheers, Rob.
    Thursday, March 04, 2010 10:08 AM