IMO, we need Royale to work on IE11.  It does not mean that Jewel must
work on IE11, but it would be nice if some theme did, other than Basic.

It turns out that my colleagues can't be sure of their data since IE was
mostly being used for intranet apps in large enterprises, but I think IE
is being kept around for those large enterprises who are leveraging the
"plug-in" capabilities of IE.  And I believe that Royale can be attractive
to those enterprises.

There is a difference between browsers that folks use for browsing the web
and the app that is used in a mission critical app for the front end.  I
think MS is saying to use Edge for the first case, but IE is going to be
around for many more years for the second case.

Does MDL and Bootstrap work on IE?  If so, if you can spend a day figuring
out why IE11 doesn't work and come up with a simpler variant that does
work, I think that would benefit Royale.

My 2 cents,

On 4/7/18, 12:42 AM, " on behalf of Carlos Rovira"
< on behalf of> wrote:

>since I'm on Mac I was blind to Microsoft browsers.
>I was testing mainly with Chrome (since is the most used) and Safari
>is what I use to use).
>I have installed Firefox, but I was not testing in a day by day basis.
>Never used Opera and Yandex since I doesn't think as relevant
>For me Browserstack is mostly to test IE11 and Edge, and I found that
>Edge has some issues (and Firefox too), both can be fixed for Jewel
>But the surprise was IE11.... this browser is not even near of what it
>should show, so taking into account that IE is facing its extinction I
>don't think I should
>put hours in make that browser work at all. For me IE is the piece of
>software we should help to be death and buried, since if it's not capable
>of rendering
>just a simple button right without lots of hacks, don't want to imagine
>what other horrors it deserve to us in this journey.
>It's clear that today IE11 has still an important demographic, but in a
>year I expect to be cut in favor of Edge that is the MS bet for the
>For me it's not aceptable to need lots of work for only one browser (an
>version), when users have Chrome, Firefox, Opera, Safari and Yandex and
>even more
>To see what I refer I think you should take a test of JewelExample in
>different browsers. All behaves more or less the same. I see some issues
>Edge and Firefox
>to fix, but if you see the example in IE11 you will literally cry...
>So what do you think?
>Carlos Rovira

Reply via email to