Re: [gwt-contrib] GWT 2 Roadmap as it applies to future deprecations

2022-08-07 Thread stockiNail
In my opinion, my 2 cents, the support of JAVA 8 and IE11 should be dropped because very close to be obsoleted. Whoever is using these platforms could stay on current version of GWT where they are supported. I still have some applications based on Java 8 but they will remain with GWT 2.8.2 and

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

2020-06-12 Thread stockiNail
rt. > > -- > Colin Alworth > co...@colinalworth.com > > > > On Fri, Jun 12, 2020, at 9:49 AM, stockiNail wrote: > > Some frameworks can support IE8 polyfilling the application. In my opinion > the IE 8 support could be dropped. > > Don't forget that the propos

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

2020-06-12 Thread stockiNail
/docs.microsoft.com/en-us/deployedge/microsoft-edge-supported-operating-systems, >> >> which says that the two OS versions (Win Server 2008 IA64 and SP2) which >> support IE9 are no longer supported, suggesting that aside from some >> specialized support contract, IE8, IE9,

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

2020-06-11 Thread stockiNail
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, only JSInterop objects. I'm writing an object (JsType native) in order to configure a chart for Chart.js. @JsType(isNative = true,