> Fwiw: IE11 will be EOL for mainstream in October this year:
> https://www.swyx.io/writing/ie11-eol/ (of course, for enterprise
> customers this will be longer; my opinion is that those companies that have
> enough money to pay for special Microsoft support contract could also pay a
>
We don't have any need to support any IE at this point.
On Thursday, June 11, 2020 at 2:08:48 PM UTC-4, stockiNail wrote:
>
> Hi all,
>
> I was facing an annoying issue about the hashcode *$N* property, stored
> inside the java script object.
>
> I'm using GWT 2.8.2 but no JSNI implementation,
Hi!
I think old browsers shouldn't be supported any more. If somebody needs
them, they should use GWT 2.9.0, which is perfectly fine and works well now
and in the future.
But for future versions of GWT, drop support for old browsers so
development can be focused on modern generations of
Working in the bankings sector. We support all IE versions that are still
available with a (payable) supported version of Windows.
So for us it is IE11 and Edge.
On 14 Jun 2020, 07:38 +0200, Alberto Mancini , wrote:
> Hi,
> I think that keeping just IE11 is ok.
>
> Thanks,
> Alberto
>
> >
Hi,
I think that keeping just IE11 is ok.
Thanks,
Alberto
On Sun, Jun 14, 2020 at 5:30 AM Freddy Boucher
wrote:
> Hi,
> On our side, an enterprise GWT webapp, 14% of our Users still use IE11 (we
> already dropped prior IE versions).
> And unfortunately we still have to support IE11 for some
Hi,
On our side, an enterprise GWT webapp, 14% of our Users still use IE11 (we
already dropped prior IE versions).
And unfortunately we still have to support IE11 for some time.
Regards
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To
Hi,
On our side, an enterprise GWT webapp, 14% of our Users still use IE11 (we
already dropped prior IE versions).
And unfortunately we still have to support IE11 for some time.
Regards
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To
It looks like even Microsoft removed support for IE<11 in their web
properties:
https://support.office.com/en-us/article/which-browsers-work-with-office-for-the-web-ad1303e0-a318-47aa-b409-d3a5eb44e452
Salesforce is going to remove IE11 and non-Chromium-based MS Edge support
at the end of this
Remove support for IE8, IE9 & IE10, keep IE11 supported. Think, most of
business users have updated to IE11 or Edge.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an
Even IE11 is not needed anymore for my projects, there is Edge for Windows
7+, so all my customers are already upgraded.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send
I would love to see just ie11 supported.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To
Regarding the ie support: We have really a lot of large customers
(https://resources.softwareag.com/customers) in all business sectors and
also a lot of customers in the financial sector which are normally very
slow updating software. Last year we removed the support for ie8, ie9 and
ie10 for
Fwiw: IE11 will be EOL for mainstream in October this year:
https://www.swyx.io/writing/ie11-eol/ (of course, for enterprise customers
this will be longer; my opinion is that those companies that have enough
money to pay for special Microsoft support contract could also pay a
company to fork
I fully agree. Based on my experience, I'd suggest, for IE, to set the
minimum supported version at IE11.
Il giorno venerdì 12 giugno 2020 17:48:48 UTC+2, Colin Alworth ha scritto:
>
> Agreed that this fix only requires dropping IE8, but I'm suggesting that
> we go a bit further and either a)
Agreed that this fix only requires dropping IE8, but I'm suggesting that we go
a bit further and either a) also drop other dead browsers, or b) have a
plan/timeline for when we can drop those browsers - at least officially. We
might still leave in support for them (as we did for IE6 for some
Some frameworks can support IE8 polyfilling the application. In my opinion
the IE 8 support could be dropped.
Don't forget that the proposal (the* Object.defineProperty()*usage) is
available from IE9, therefore we are not saying that we raise the GWT
requirement to IE11 or Edge, but only 1
Most of our cliensts dropped support for ancient IEs, and we now only
support IE11 and edge.
On Thursday, June 11, 2020 at 10:18:18 PM UTC+3, Colin Alworth wrote:
>
> Since the existing code is very similar to J2CL's code, it seems like a
> reasonable change, provided it is indeed safe to drop
Since the existing code is very similar to J2CL's code, it seems like a
reasonable change, provided it is indeed safe to drop support for IE8. At a
glance, I'm having trouble finding a recent statement describing whether or
not IE8 (and 9, 10) ought to be supported - since GWT is often used for
18 matches
Mail list logo
