John Price reported this issue when creating an Issue tab plugin that uses an iframe in JIRA 4.1:

      I have an issue tab panel plugin that displays an iframe with content from our company web site, In my test upgrade to 4.1, it causes "Permission Denied" javascript errors to pop up when the panel is clicked. This is in IE only (version 8). It worked fine in JIRA 4.0, and it also works fine in FF with JIRA 4.1.

      When debugging, the error is coming from a file called ajs.js, which must be part of the JIRA installation.

      I've been able to validate this on a local test system. In JIRA 4.0, there are no errors in IE8. In JIRA 4.1, the Javascript error appears. This is using the same plugin JAR file.

      John has also been kind enough to provide a simple test Issue tab plugin that attempts to display Wikipedia in an iframe, which I have attached to this issue. To reproduce:

      Here are the steps to reproduce:

      • install the plugin in JIRA 4.1. It shows up as "iFrame Test" in admin.
      • open JIRA in Internet Explorer 8.
      • Go to any issue and click the "iFrame Tab Panel" tab.
      • You should get a javascript error.

      John initially created this forum post to resolve his issue but received no responses.

        1. iframeTest-1.0-SNAPSHOT.jar
          5 kB
        2. screenshot-1.jpg
          screenshot-1.jpg
          32 kB
        3. screenshot-2.jpg
          screenshot-2.jpg
          569 kB

            [JRASERVER-21348] JIRA 4.1 Breaks Custom Plugin That Uses an iframe

            John Price added a comment -

            Any idea when this might get fixed? Because we have a plugin that uses an iframe, we can no longer upgrade JIRA at all and are cut off from new features. We're perma-stuck at 4.0 (old issue screen) until this is fixed or a workaround is posted.

            John Price added a comment - Any idea when this might get fixed? Because we have a plugin that uses an iframe, we can no longer upgrade JIRA at all and are cut off from new features. We're perma-stuck at 4.0 (old issue screen) until this is fixed or a workaround is posted.

              Unassigned Unassigned
              dhansen@atlassian.com Dylan Hansen [Atlassian]
              Affected customers:
              2 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: