[gwt-contrib] Re: HashCode H$ property should be not enumerable

['Frank Hossfeld' via GWT Contributors]

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 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/398a11a8-bbd4-48a5-82fe-5faf0a4af2fco%40googlegroups.com.

Re: [gwt-contrib] Re: HashCode H$ property should be not enumerable

[Thomas Broyer]

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 year for their Lightning Experience (
https://help.salesforce.com/articleView?id=getstart_browsers_sfx.htm&type=5) 
but keep IE11 longer for Salesforce Classic (
https://help.salesforce.com/articleView?id=getstart_browser_aloha.htm&type=5, 
which doesn't support the Chromium-based MS Edge though). Note that IE11 
support in Lightning is an option since December 2017, and it isn't 
supported in all Salesforce features (
https://help.salesforce.com/articleView?id=getstart_browser_considerations_ie.htm&type=5
)

Google G Suite doesn't support IE<11: 
https://support.google.com/a/answer/33864?hl=en
Google Maps JavaScript API still supports IE10 but it's going to be removed 
really soon (if not already): 
https://developers.google.com/maps/documentation/javascript/browsersupport
It's not clear what versions of IE are supported for Google Maps (
https://support.google.com/maps/answer/3118069?hl=en, 
https://support.google.com/maps/answer/3096703?hl=en, which says that 
Windows XP is supported but also says to update to the latest IE version; 
it's likely that only Firefox is supported on Windows XP)

I know nothing of SAP, but it looks that they dropped support for IE8, and 
selectively also dropped support for IE9 and IE10, or even IE11 (and 
non-Chromium Edge), depending on the product: 
https://help.sap.com/viewer/38b8eafc22cf44cfbe2e5eed5631b1b2/3.0/en-US/a430e8d8a0ac4333ae1d4d5f989d3fa6.html
, 
https://help.sap.com/viewer/62383e3f14f34e2296cd3ddc8cb231f8/Cloud/en-US/0741076fccab4f99bf3fbce88b6d2f97.html
, 
https://help.sap.com/viewer/5b0a45d84713461084c26b6a31533fd0/cloud/en-US/c833bc3cc92645959797d5a020ede514.html
, 
https://help.sap.com/viewer/03a5c8e659494e51b4cd694c4d0c8894/Cloud/en-US/3dc13139e53648f1841ba9c3295b870d.html
, 
https://help.sap.com/viewer/299eb67442cc4e308cd40b2a2551af8c/Cloud/en-US/137996fb5c364e78b78b965408113f3d.html

Alfresco requires IE11 too: 
https://docs.alfresco.com/6.2/concepts/supported-platforms-ACS.html

That was off the top of my head of Enterprise products used by big 
companies that are likely to lag behind due to a huge number of IT assets.

On the communication side, Twitter doesn't support IE (
https://help.twitter.com/en/using-twitter/twitter-supported-browsers), same 
for Youtube (https://support.google.com/youtube/answer/175292?hl=en), and 
Facebook (https://www.facebook.com/help/210310575676558)

Looking at other Web "development kits", Angular requires IE9+ (
https://angular.io/guide/browser-support), and React too (
https://reactjs.org/docs/react-dom.html#browser-support, and even requires 
additional polyfills for IE9 and IE10)

My opinion, if it wasn't clear in my previous message: we could drop 
support for IE<11.
That's going to require some work though, so let's begin with removing IE 8 
support with this change to ObjectHashing, without necessarily removing the 
ie8 permutation for now. An alternative would be to reintroduce 
EmulationWithUserAgent to use Object.defineProperty wherever it's supported 
and keep the current behavior in the ie8 permutation.

On Friday, June 12, 2020 at 8:45:10 PM UTC+2, Thomas Broyer wrote:
>
> 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 and maintain GWT for those usecases; or they can just stay 
> on an old version of GWT like they're staying on an old version of IE; 
> those companies are not my customers though so my opinion probably doesn't 
> weight much)
>
> Also, jQuery dropped support for IE8 while back and is now IE9+ 
> https://jquery.com/browser-support/. That supports the option for GWT to 
> do the same, at a minimum.
>
> Finally, several "modularized gwt-user" modules already dropped support 
> for IE8 and IE9 AFAICT, possibly even IE10.
>
> On Friday, June 12, 2020 at 5:53:56 PM UTC+2, stockiNail wrote:
>>
>> 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) 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 
>>> years), but require that projects go out of their way to enable that 
>>> support.
>>>
>>> -- 
>>>   Colin Alworth
>>>   co...@colinalworth.com
>>>
>>>
>

Re: [gwt-contrib] Re: Ant, ZipScanner, and GWT

[Thomas Broyer]

On Friday, June 12, 2020 at 11:05:34 PM UTC+2, Colin Alworth wrote:
>
> So, given either "make a git repo on gwtproject/ and add a jar to 
> gwtproject/tools" with the minimal history, or a single commit adding all 
> already-modified classes to gwt in one go? I should be able to turn out 
> either change fairly quickly, once we decide.
>
> Adding to GWT directly would be somewhat lower friction (no need to ship a 
> jar to central, easier to further tweak if something is screwy), but as I 
> said, loses that tiny bit of history/context. Like you said, a forked jar 
> is not at all new for the project to have, and is a nice way to say "this 
> is external, even if we tweaked it a bit". For the zip distribution I 
> imagine we'd shade it in to the overall zip, but for the m2 release it 
> would probably be an external jar (since it will hopefully never change).
>

If you're worried about the size of the JAR, let's kill legacy DevMode 
instead ;-)
(Google possibly even has the patch ready, as IIRC they already removed it 
in their internal repository)
Let's keep it simple and just ship it inside the gwt-dev JAR; our other 
repackaged dependencies are in there already (protocol buffer, 
streamhtmlparser, GSS, Guava, jscomp –for sourcemaps–, etc.)

-- 
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/99e84a33-371a-4e26-bdb2-a542bd2c9dfco%40googlegroups.com.

[gwt-contrib] Re: HashCode H$ property should be not enumerable

[Freddy Boucher]

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 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/f19cc9d0-8f67-4cd1-9b41-e8b9117ab92fo%40googlegroups.com.

[gwt-contrib] Re: HashCode H$ property should be not enumerable

[Freddy Boucher]

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 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/8bb390c7-855e-455e-bb34-16b6d18f6452o%40googlegroups.com.

Re: [gwt-contrib] Re: HashCode H$ property should be not enumerable

[Alberto Mancini]

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 time.
> Regards
>
> --
> 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/8bb390c7-855e-455e-bb34-16b6d18f6452o%40googlegroups.com
> 
> .
>

-- 
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/CAGv30Vmb7%2BHwMr%2BkZfS72ZPSSi%2BQ8DXLy%3DtR-ib-zda_-Bi%3DPQ%40mail.gmail.com.