Note about browser support?

[getmeuk]

Note about browser support?

[anthonyjb]

You're right that's something I need to add to the repo READMEs and the API docs. To help answer your question ahead of that:

Browser support
The current aim is for all the libraries to support IE9+, Chrome and Firefox. Test suites are complete for all the libraries accept ContentTools and I'm using Jasmine to check that the tests pass in those browsers.

There will be some visual differences for ContentTools in IE9 as I use CSS animations for some of the UI feedback.

My current development priority is to complete the test suite for ContentTools.

Underlying API

So whenever text is being edited then the contenteditable attribute is appended to the element (or a wrapper element in the case of table dimensions and list items - thank you IE for that doozy). Even so the output of the contenteditable element is marshalled using the HTMLParser library to ensure that the content output is consistent and not browser specific.

As for polyfills the only one I can think of is:

HACK: Add constructor name property to IE9+, code based on the stackoverflow 
response http://stackoverflow.com/a/17056530

View source

There are a number of helper functions provided to support functionality in a consistent way across all browsers (such as adding and removing CSS classes) but they don't overwrite native browser behaviour.

[dburrows]

I had the same question and this is a great explanation, think you can just add the two paras above to the README with a quick edit

[butsjoh]

I agree with @dburrows 👍

[anthonyjb]

Thanks for the feedback @butsjoh and @dburrows.