You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Bonfire Browser Extension

This section details any known issues we have with the browser extension including those caused by upstream bugs from the browser itself.

Cross Browser Upstream Bugs

Most of these upstream bugs relate to elements of a page that aren't captured correctly in the screenshots. This is because we rely on the individual browser APIs for the screenshots.

Bonfire IssueDescription of the problemVendor IssueWorkaround (If any)
BON-367 - Getting issue details... STATUS Problems capturing Java applets using Bonfire. A blank screen is returnedhttp://code.google.com/p/chromium/issues/detail?id=51474

More information: Bonfire Compatibility Chart

BON-422 - Getting issue details... STATUS Bonfire does not work in pop-up windows.https://bugzilla.mozilla.org/show_bug.cgi?id=375679
https://bugzilla.mozilla.org/show_bug.cgi?id=302288		More information: Bonfire Compatibility Chart
BON-659 - Getting issue details... STATUS Problems capturing Unity3D applications. Blank screen is returnedNone

More information: Bonfire Compatibility Chart

BON-1027 - Getting issue details... STATUS

BON-1216 - Getting issue details... STATUS

Bonfire does not always capture flash.NoneMore information: Bonfire Compatibility Chart
BON-236 - Getting issue details... STATUS Bonfire does not always capture Silverlight.NoneMore information: Bonfire Compatibility Chart

Safari Upstream Bugs

Bonfire IssueDescription of the problemVendor IssueWorkaround (If any)
BON-1401 - Getting issue details... STATUS Taking a screenshot in Safari 6 does not take scrolling into accountRadar ID #12193958None
BON-1544 - Getting issue details... STATUS Rectangle annotations can't be selected or movedNone – This is a bug in WebKitNone

Internet Explorer - Known Issues relating to injection into the page

All bugs listed here are related to the annotation tools being injected into the page in IE. Currently we do not have a solution for including the annotation tools into the page without injection.

Bonfire IssueDescription of the problemBrowser IssueWorkaround (If any)
BON-240 - Getting issue details... STATUS

This problem is caused by the fact that, in Internet Explorer, the screenshot and annotation tools sit within an iframe that needs to be injected into the web page. Firefox, Chrome and Safari have different extension points and APIs, and allow other solutions for showing the screenshot that don't touch the page under test.
In IE, the iframe is attached to the document.body DOM node - but pages with full-page <frameset> elements (not iframes) don't have a document.body node (reading the property returns null).

After discussions with other developers I've tried a few different methods of injecting the screenshot iframe into a frameset page, unfortunately none of them worked.

  • Appending the iframe to the frameset element does nothing
  • Appending to the document node causes a "Catastrophic failure" error message
  • Appending to the HTML element (document.documentElement) is valid (and works in Chrome), but displays nothing in IE and causes an "Out of memory" error when trying to generate the screenshot.

The conclusion appears to be that unless we have some way of showing the screenshot WITHOUT injecting into the page, there's no real way around this problem. Investigations into showing the screenshot without page injection have so far not been promising.

NoneNone
BON-441 - Getting issue details... STATUS Bonfire does not work properly in Quirks mode. This is expected given Quirks mode is IE5. Bonfire only supports IE7-9 currently.NoneDon't use Quirks mode.
BON-152 - Getting issue details... STATUS Websites that use HTTPS throw a warning when there is mixed content on the page. Getting the screenshot from the page causes one such warning and if the internet settings of the browser forbid mixed content, then the annotation tools will never workNoneAllowing mixed content

JIRA - Upstream Bugs

Bonfire IssueDescription of the problemJIRA IssueWorkaround (If any)
  BON-301 - Getting issue details... STATUS

This problem only affects JIRA Studio customers

When authenticating Bonfire to a GApps-enabled Studio instance, the password required is not the GApps password but the JIRA Studio password.

Bonfire authenticates with JIRA using the REST authentication API and that API does not allow GApps login. Therefore those credentials cannot be used to login to Bonfire

 NoneUse Studio Login 
  • No labels

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.