My preference would still be to keep IE11, for one more year, if possible. https://blogs.windows.com/windowsexperience/2021/05/19/the-future-of-internet-explorer-on-windows-10-is-in-microsoft-edge/ MS official suport ends on June 15, 2022.
Is there some new feature to be added, into GWT core that require removal of IE11? +1 removal of ie8-10. +1 deprecate ie11 for gwt 2.10 On Thursday, September 30, 2021 at 7:49:56 PM UTC+3 nilo...@gmail.com wrote: > I've just filed https://github.com/gwtproject/gwt/issues/9739, where a > workaround exists in java.util.Date that nearly doubles the time it takes > to parse date strings and build date objects. This workaround exists for > IE8 and IE9, as all more recent browsers implement the same behavior as we > already would expect. Dropping support for those two browsers would > simplify the code required here > > From the age of this thread and the discussion so far, it sounds like > there is interest in keeping IE11 still, but no one has spoke up about IE10 > or below. > > Additionally, java.util.Random emulation was changed to require > Date.now(), which isn't available in IE8, so neither GWT 2.8.2 nor GWT > 2.9.0 are apparently compatible with IE8 anyway, at least in this small > way. This should give us some confidence (along with the lack of opposition > in this thread) that at least IE8 is definitely safe to drop. > > So, is there any objection at this time to dropping what remains of IE8, > IE9, and IE10 support from GWT? Then, we can reevaluate IE11 at some later > date, for GWT itself? Various migrated GWT modules have focused their > efforts on well-supported browsers, and are likely to only support IE11 by > accident anyway. > > On Friday, March 12, 2021 at 1:20:02 AM UTC-6 stuckagain wrote: > >> We still need IE11 support in the banking sector. We still have a >> majority of customers that use IE11 due to technical reasons (plugins >> needed for accessing secure token donβt install properly in Chrome without >> internet access amongst others). >> >> What do you mean with βnext version of GWTβ if that is 3.x then I donβt >> care at this point. We have been waiting for that release for a few years >> now. But 2.x releases should not drop IE11 support it is supposed to be a >> long-term supported version. >> On 12 Mar 2021, 07:54 +0100, bernhar...@schubec.com < >> bernhar...@schubec.com>, wrote: >> >> Hi all! >> >> I think IE11 support should be dropped soon if it blocks (or makes it >> difficult) to implement new features in the next version of GWT. >> I understand, that there are enterprises who still use IE11 internally, >> but developers who service such enterprises should use the current version >> of GWT, which is not going away. Nobody is forced to upgrade to the next >> version of GWT. >> >> Thanks, >> Berni >> >> tony.be...@gmail.com schrieb am Donnerstag, 11. MΓ€rz 2021 um 22:26:21 >> UTC+1: >> >>> IE 11 is still widely used inside corporations, because it is the only >>> browser that supports Java applets, and applications such as Oracle >>> e-Business Suite still use applets extensively (for Oracle forms). While >>> that segment does not move very fast, it does not mean other unrelated >>> groups within the same corporation are not updating GWT regularly. It is >>> hard to generalize In a multinational company with tens of thousands of >>> employees. >>> >>> Regards >>> >>> Tony >>> >>> On Thu, Mar 11, 2021 at 9:49 AM Jens <jens.ne...@gmail.com> wrote: >>> >>>> Dropping IE 8-10 shouldn't really hurt. Companies that require it are >>>> probably not upgrading GWT in a fast pace anyways. >>>> >>>> However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to the >>>> lifecycle of Microsoft's operating systems, which means for Windows 10 it >>>> is supported until 2025 (for now). So just because MS and Google drop >>>> support for IE 11 in some/all of their products, the browser itself is >>>> still generally supported by MS. So we should think twice before removing >>>> IE 11 from a library such as GWT, even if it means to decline/revert >>>> certain commits if they break IE 11. From own experience I have usually >>>> seen something around 8% of IE 11 usage in GWT based apps. >>>> >>>> However I am pretty sure more and more companies will announce dropping >>>> IE 11 this year or next year. With MS and Google starting, this could >>>> easily have a domino effect. However GWT also also strongly used >>>> internally >>>> inside companies so it might not have that much of an effect in that area. >>>> >>>> If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we kill >>>> them both as well and put them together? Are there so many differences in >>>> code between both? From my work migrating GWT code to elemental2/JsInterop >>>> I had the feeling that only some minor stuff is different between both. So >>>> there shouldn't be that much overhead in code size and performance doing >>>> (cached) runtime checks instead. >>>> >>>> -- J. >>>> >>>> -- >>>> 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-co...@googlegroups.com. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/031f1171-cce9-4c17-b717-80bb5730f7fdn%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/031f1171-cce9-4c17-b717-80bb5730f7fdn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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-co...@googlegroups.com. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit-contributors/99f9b82a-a56c-4c3e-b980-e3160581a486n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/99f9b82a-a56c-4c3e-b980-e3160581a486n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/462af217-5b41-45c2-afeb-8bac0a07c80dn%40googlegroups.com.