Question

Currently, I have an issue with populating an iframe that I have with a PDF document, but this issue only occurs in IE.

Basic Layout:

I have a screen that contains a list of items (attachments), which can be images, text or pdf. When the user clicks on one of these items – it will make a call to a controller action [ViewAttachment] which will return the requested item and display it in the iframe.

This currently works for all data types with the exception of PDFs in IE. (Firefox, Chrome etc. all display the PDF in the iframe without issue.)

I previously was using Adobe Reader 9, and recently upgraded to 10 in hopes of solving this issue. I’ll attach some code to see if anyone has any suggestions as to how to possibly resolve this.

Code to Populate iframe: (Moved to two lines for readability)

$(".viewattachment").live('click',function () 
{ 
   $("iframe#test").attr("src","<%=Url.Action("ViewAttachment","Images") %>?
   attachment=" + $(this).next().val());
}); 

ViewAttachment Controller Action:

public ActionResult ViewAttachment(string attachmentGuid)
{
      Attachment attachment= imageAgent.GetAttachment(attachmentGuid);

      Stream resultStream = new MemoryStream();
      resultStream =  StorageProviders[attachment.ProviderName]
                      .ReadFile(attachment.FileReference);

      resultStream.Position = 0;
      FileStreamResult result = new FileStreamResult(resultStream, 
                                                     attachment.ContentType);

      return result;
}

Notes:

• I’ve attempted toggling the “Display PDF in Browser” in Adobe Reader without any success.
• Currently testing this for IE8.
• When clicking on a PDF to view – the iframe simply remains at it’s previous content and doesn’t change at all.

Answer 1

After several different methods and iterations of testing – I determined that it was a conflict between IE8-9 and versions of Adobe Reader 9-10. I added the following meta tag to the window containing the iframe and it resolved all of the issues:

<meta http-equiv="X-UA-Compatible" content="IE=7" />

This should at least work until an update / fix is made.