Tuesday, July 7, 2026

Re: Elemental2 oddities

With the Elemental2 1.4.0-RC1 release, we now have a new WebGLContextAttributes class that now has a create method.

However, calling it:
WebGLContextAttributes contextAttributes = WebGLContextAttributes.create();

Results in:
com.google.gwt.core.client.JavaScriptException: (ReferenceError) : mOu_g$ is not defined

Which isn't what I expected.

Doing this still works:
WebGLContextAttributes contextAttributes = Js.uncheckedCast(JsPropertyMap.of());

I don't have the closure compiler knowledge to understand what's going on here.  Was the fix ( https://github.com/google/closure-compiler/issues/4250 ) not correct?

On Monday, 28 July 2025 at 8:20:37 pm UTC+10 Craig Mitchell wrote:
Thanks again Jens.  Issue raised:  https://github.com/google/closure-compiler/issues/4250

On Monday, 28 July 2025 at 6:55:23 pm UTC+10 Jens wrote:
Because it is only a dictionary (= a plain JS object)


In JS you simply do:

var canvas = document.getElementById('canvas');
var context = canvas.getContext('webgl', { antialias: false, stencil: true }); // 2nd argument is WebGLContextAttributes
var attributes = context.getContextAttributes();

Looks like it is again defined badly in closure-compiler externs. The generated elemental2 implementation should have a similar structure than for example elemental2 AddEventListenerOption. It is an interface with a static create() method which does exactly what you do in your solution.

See:


I think it should be @interface or @record instead of @constructor.


-- J.

Craig Mitchell schrieb am Montag, 28. Juli 2025 um 07:39:57 UTC+2:
I'm switching to use Elemental2, and it's fantastic.  All the bindings I'll ever need.  A big thank you to all that created it!

There are some strange things though.  Like when setting up a WebGLRenderingContext, we need to pass WebGLContextAttributes.

However, doing:
WebGLContextAttributes contextAttributes = new WebGLContextAttributes();

compiles fine, but at runtime throws:
TypeError: $wnd.WebGLContextAttributes is not a constructor

I figured out I can do this instead:
WebGLContextAttributes contextAttributes = Js.uncheckedCast(JsPropertyMap.of());

But why can't I just use its constructor?  Am I doing something wrong?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/126d9f3a-513b-4aeb-bd33-1adccce25605n%40googlegroups.com.

Re: Elemental2 WebRTC createOffer and createAnswer are incorrect

It took a year, but the newly released Elemental2 1.4.0-RC1 now has this fix.  🎉

On Wednesday, 20 August 2025 at 9:40:32 am UTC+10 Craig Mitchell wrote:
Following up on my own comment:  A request for a new build with updated closure externs has been made:  https://github.com/google/elemental2/issues/175

On Sunday, 20 July 2025 at 9:37:31 am UTC+10 Craig Mitchell wrote:
Now the good people at the closure-compiler have fixed the error ( https://github.com/google/closure-compiler/commit/5aadfa78592a2778ae4cac52613fb9238228b3e8 ), I see I can build a new version of Elemental2 locally ( https://github.com/google/elemental2?tab=readme-ov-file#build-gwt-compatible-maven-jar-files ).

It would be nice to get an offical Elemental2 build, and have it pushed to Maven.  It looks like one hasn't been done for 9 months, is there any offical Elemental2 release schedule?

On Tuesday, 15 July 2025 at 7:37:27 pm UTC+10 Craig Mitchell wrote:
Thanks Jens.  Bug raised:  https://github.com/google/closure-compiler/issues/4249

On Tuesday, 15 July 2025 at 6:49:06 pm UTC+10 Jens wrote:
And this works great.  But it would be nice to fix Elemental2.

You have to file an issue against closure-compiler because elemental2 takes their definition: https://github.com/google/closure-compiler/blob/15c5dd492cbb9dcdfd24d01f75b64e3e9b2291eb/externs/browser/w3c_rtc.js#L3586C23-L3586C44

-- J. 

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/4cb68587-ffe6-40e2-8153-6e0d56bb291bn%40googlegroups.com.

Monday, July 6, 2026

Learn more about our updated Terms of Service

Monday, June 22, 2026

Re: GWT 2.13.1 released

Looks good here too (rebuild with GWT 2.13.1 SDK in Eclipse 2026-06 with the GWT Eclipse Plugin).

On Friday, June 19, 2026 at 8:50:36 PM UTC-7 Craig Mitchell wrote:
Working great here too.  Thank you!

On Saturday, 20 June 2026 at 7:38:37 am UTC+10 Juan Pablo Gardella wrote:
Great! My apps worked well with that version, thanks!

On Fri, Jun 19, 2026 at 4:22 PM Colin Alworth <co...@colinalworth.com> wrote:
This is a small bugfix release, with four changes:

  • Permit failure to delete files on Windows, and close finished logs. This is a regression, caused by trying to use Guava to replace some bespoke utility classes.
  • Simplify RTA iframe loading in Firefox. This addresses a change in behavior in Firefox, although in most cases applications compiled with older versions of GWT should have a workaround automatically applied by Firefox.
  • Use Objects.equals to compare record fields for null support. As the current implementation of records was producing an incorrect equals method and this was a low risk fix, this was backported.
  • Include GWT version, commit in JFR output. This ensures that we have a baseline for compiled size improvements going forward.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/9659b3ed-e134-4ea3-88c5-995ecd3919f5n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/88b5f5ff-e209-4ac5-98ae-8c3593ee9558n%40googlegroups.com.

Friday, June 19, 2026

Re: GWT 2.13.1 released

Working great here too.  Thank you!

On Saturday, 20 June 2026 at 7:38:37 am UTC+10 Juan Pablo Gardella wrote:
Great! My apps worked well with that version, thanks!

On Fri, Jun 19, 2026 at 4:22 PM Colin Alworth <co...@colinalworth.com> wrote:
This is a small bugfix release, with four changes:

  • Permit failure to delete files on Windows, and close finished logs. This is a regression, caused by trying to use Guava to replace some bespoke utility classes.
  • Simplify RTA iframe loading in Firefox. This addresses a change in behavior in Firefox, although in most cases applications compiled with older versions of GWT should have a workaround automatically applied by Firefox.
  • Use Objects.equals to compare record fields for null support. As the current implementation of records was producing an incorrect equals method and this was a low risk fix, this was backported.
  • Include GWT version, commit in JFR output. This ensures that we have a baseline for compiled size improvements going forward.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/9659b3ed-e134-4ea3-88c5-995ecd3919f5n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/81042bec-ad81-46f8-ac67-ef228bca6d5bn%40googlegroups.com.

Re: GWT 2.13.1 released

Great! My apps worked well with that version, thanks!

On Fri, Jun 19, 2026 at 4:22 PM Colin Alworth <colin@colinalworth.com> wrote:
This is a small bugfix release, with four changes:

  • Permit failure to delete files on Windows, and close finished logs. This is a regression, caused by trying to use Guava to replace some bespoke utility classes.
  • Simplify RTA iframe loading in Firefox. This addresses a change in behavior in Firefox, although in most cases applications compiled with older versions of GWT should have a workaround automatically applied by Firefox.
  • Use Objects.equals to compare record fields for null support. As the current implementation of records was producing an incorrect equals method and this was a low risk fix, this was backported.
  • Include GWT version, commit in JFR output. This ensures that we have a baseline for compiled size improvements going forward.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/9659b3ed-e134-4ea3-88c5-995ecd3919f5n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CA%2BkiFseg6CXhCOZ_5X8s57J-oQRZo-kRxGQwCWcPEfHm3KxQOA%40mail.gmail.com.

GWT 2.13.1 released

This is a small bugfix release, with four changes:

  • Permit failure to delete files on Windows, and close finished logs. This is a regression, caused by trying to use Guava to replace some bespoke utility classes.
  • Simplify RTA iframe loading in Firefox. This addresses a change in behavior in Firefox, although in most cases applications compiled with older versions of GWT should have a workaround automatically applied by Firefox.
  • Use Objects.equals to compare record fields for null support. As the current implementation of records was producing an incorrect equals method and this was a low risk fix, this was backported.
  • Include GWT version, commit in JFR output. This ensures that we have a baseline for compiled size improvements going forward.

  • --
    You received this message because you are subscribed to the Google Groups "GWT Users" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
    To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/9659b3ed-e134-4ea3-88c5-995ecd3919f5n%40googlegroups.com.