Statement on IE

[timhaines]

I noticed the main readme and the browser inconsistencies page both lack any mention of IE (Internet Explorer).

I'm wondering what Scribe's position is on it? Is a certain version of IE supposed to be supported, or is it completely unsupported?

[OliverJAsh]

See #151

[timhaines]

@OliverJAsh That doesn't mention IE either. I'm still unclear the the questions I asked..

[OliverJAsh]

Older browsers == IE.

We don't support it because it doesn't provide the necessary APIs, but there is work that can be done to add support for it (see #151 for suggestions). You can track our stance on this in the issue I linked you to, as it will likely change over time. Sorry.

[theefer]

We're happy to accept patches that would improve compatibility with unsupported browsers of course, as long as they don't require fundamental tainting of the framework. I'd hope more recent IEs (10+) would not be too bad, but I don't have any experience with those "unfortunately".

[timhaines]

@OliverJAsh @theefer Thanks guys. I was wondering if you put IE11 in that Older Browsers basket too.

It's great to get a clear statement from you that it's not supported currently. That lets us make some informed decisions..

[philcockfield]

Older browsers == IE

We pretty much had the same approach with Respondly and chose to just not support IE. Then we were flabbergasted to find that the project "just worked" on IE11.

However, that being said, as I've delved into manipulating content-editable in IE11, it's still in a world of pain when it comes to operating on the selection/range and document.execCommand related API's.

I'd imagine (read "hope") that if no special support for IE was done, but if Scribe contined down it's path of conforming to the standardized, or "standardizing" commands (as per #151) that at some point soon IE would just start working.

[OliverJAsh]

That’s the dream, @philcockfield 😄