Reporting a bug

Where to Find Known Issues

We are using GitHub Issues for tracking any bugs. Before filing a new bug, please try to make sure a GitHub issue does not already exist for it.

Security Bugs

If you have a security question or issue to report, please email origami.support@ft.com, please do not file public issues for any security issues which are sensitive such as a stored cross-site-scripting vulnerability.

Reporting New Issues

The sections below outline some common scenarios and how to help create good bug reports for them.

The polyfill bundle is causing an error in your app

You've got an error in your website that you've tracked down to the code you're loading from the polyfill service.

The best way to get your bug fixed is to provide a reduced test case. We ask for a reduced test case because occassionally the problem is not from polyfill.io but from the host website's code.

Raise a new issue on our issue tracker, and include:

A polyfill is not correctly/completely emulating the missing feature

You've found a polyfill which you believe is not working correctly.

The best way to get your bug fixed is to provide a reduced test case. We ask for a reduced test case because occassionally the problem is not from polyfill.io but from the host website's code.

Raise a new issue on our issue tracker, and include:

A particular polyfill is being served to a browser that does not require the polyfill

You've found that a browser is being served a polyfill for a feature that it does not need.

Raise a new issue on our issue tracker, and include: