Skip to content

Browser Support

Active Support

We support all major web browsers. Any issue in the browsers listed below should be reported as a bug.

  • Internet Explorer 9+
  • Safari 6+
  • Firefox (Current - 1) and Current versions
  • Chrome (Current - 1) and Current versions
  • Opera (Current - 1) and Current versions
  • iOS 6.0+
  • Android 4.0+

(Current - 1) and Current means that we support the current stable version of the browser and the version that precedes it.

Starting with Froala WYSIWYG Editor version 1.2.6 we dropped the limited support for IE 8. Some of the rich text editor's features cannot be implemented in earlier versions of IE than 9. Fallback to textarea in IE 8 is expected for version 1.2.7. However, we recommend our users to upgrade to a newer version of Internet Explorer.

Unsupported Browsers

We do not offer support for pre-release versions of browsers, such as beta or dev release. If you find a bug in a pre-release of a browser, you should probably report it to the browser vendor.

Froala WYSIWYG editor may run without any major issues in older browser versions, we are not testing the rich text editor in them and we usually do not fix bugs that may appear in them.

About Browser Support

Froala Rich Text Editor is constantly tested is all the supported browsers via unit tests. However, there might be small differences from one browser to another according to the browser-specific behaviors. Testing is essential to fully support a browser. BrowserStack makes available virtual machines for testing many different browser versions on different platforms.

Only the last version of the WYSIWYG HTML editor is tested and updated to fix bugs and add features. Users of older versions that find a bug should upgrade to the latest released version to determine if the bug has already been fixed.

Fonts not Showing in Firefox

If you are working locally and testing examples using file:/// in the browser instead of running files from a web server, the icons are most likely not showing up properly. This is because Firefox has a strict "file uri origin" policy that prevents access to web fonts from folders not in the root. To fix this you have to configure Firefox by typing about:config in the address bar, and change security.fileuri.strict_origin_policy form true to false.