On Thursday, August 25, 2016 at 3:14:17 PM UTC-4, Luke Westby wrote:
>
> You're welcome! I apologize for the terseness of my previous comments, was
> in a hurry and let that get in the way of friendliness.
>
Sir, no need to apologize! Your posts are always extremely friendly and
helpful :)
You're welcome! I apologize for the terseness of my previous comments, was
in a hurry and let that get in the way of friendliness.
Anyway, it would be cool if somewhere on elm-lang.org the intended browser
support was spelled out unambiguously. It would help users understand what
support they
Don't get me started on IT departments that mandate the use of old, buggy,
insecure browsers that no longer have vendor support across their
organisations! If their users get hit with browser-based attacks that
compromise customer data the org could be liable.
It's really about finding what browsers elm code won't run on.
On the project I'm working on, IE8 is in scope because we still have a
significant number of users using it. If I want to introduce elm, it's
easier to say it runs without a problem than to say some features won't
work, or we need
It works fine at least in IE11 and Edge, of which my app is tested in and
works without issue. Do you not mean just old versions like IE8 and older
(which need to die)? Or what about 9 and 10 as well?
On Wednesday, August 24, 2016 at 10:38:39 AM UTC-6, Rex van der Spuy wrote:
>
> Just wish to
Ah, well forget everything I said then.
That sounds like it's worth opening a bug report for.
On Wed, Aug 24, 2016 at 9:38 AM, Rex van der Spuy
wrote:
> Just wish to alert everyone that Elm's port code will not work with any
> version of IE without a ployfill for
Just wish to alert everyone that Elm's port code will not work with any
version of IE without a ployfill for `Object.assign`
(https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/assign)
--
You received this message because you are subscribed to the Google