UIBinder ui:style fails when first omitted

[craigmit]

Issue: Adding a ui:style after not having one in the UIBinder causes a crash.

To reproduce:

1. Clone my demo repo: git clone https://github.com/craigmit/GwtUiBinderStyleIssue.git
2. cd GwtUiBinderStyleIssue
3. Start code server: mvn gwt:codeserver -pl *-client -am
4. Start server: mvn spring-boot:run -pl *-server -am
5. Visit page: http://localhost:8080/
6. You should see a page saying "No style"
7. Edit: test-client/src/main/java/test/TestWidget.ui.xml
8. Remove the comments, so it now looks like this:

9. Refresh the page: http://localhost:8080/

The page crashes with:

Uncaught TypeError: this.get_clientBundleFieldNameUnlikelyToCollideWithUserSpecifiedFieldOkay_0_g$(...).style_3_g$ is not a function
    at C3d_g$.F7d_g$ [as build_style_0_g$] (TestWidget_TestWidgetUiBinderImpl.java:72:1)
    at new C3d_g$ (TestWidget_TestWidgetUiBinderImpl.java:43:1)
    at w3d_g$.y3d_g$ [as createAndBindUi_1_g$] (TestWidget_TestWidgetUiBinderImpl.java:31:1)
    at w3d_g$.x3d_g$ [as createAndBindUi_0_g$] (TestWidget_TestWidgetUiBinderImpl.java:28:1)
    at new s3d_g$ (TestWidget.java:13:1)
    at o3d_g$.p3d_g$ [as onModuleLoad_0_g$] (App.java:14:1)
    at Array.J1b_g$ (test_00046App__EntryMethodHolder.java:3:1)
    at initializeModules_0_g$ (ModuleUtils.java:44:1)
    at Hp_g$ (Impl.java:293:1)
    at Kp_g$ (Impl.java:352:1)

Even if you stop everything, mvn clean, and start it back up, it still crashes.

Workaround:
The only way I've found to get it to work is to remove the style so it looks like this:

Refresh the page. Now you see the page without the style:

Got style, ayyyy!
No style

Then add the style back in (so it looks like step 8 above), and it now works:

[jnehlmeier]

Workaround:
The only way I've found to get it to work is to remove the style so it looks like this:

A workaround is to just change the field name of the style tag, e.g.

<ui:style> ---> <ui:style field="css">  // do not use "style" as name, as that is the default name

You do not have to change every {style.abc} in the xml. Just change the field name and recompile to see a different error (because {style.abc} cannot be resolved anymore). Then remove the field name again.

[craigmit]

Workaround:
The only way I've found to get it to work is to remove the style so it looks like this:

A workaround is to just change the field name of the style tag, e.g.

<ui:style> ---> <ui:style field="css">  // do not use "style" as name, as that is the default name

You do not have to change every {style.abc} in the xml. Just change the field name and recompile to see a different error (because {style.abc} cannot be resolved anymore). Then remove the field name again.

That workaround didn't work for me. When I add the field="css", I see the code server error on the recompile:

[INFO] GET /recompile/app
[INFO]    Job test.App_1_3
[INFO]       starting job: test.App_1_3
[INFO]       binding: user.agent=safari
[INFO]       Compiling module test.App
[INFO]          Computing all possible rebind results for 'test.TestWidget.TestWidgetUiBinder'
[INFO]             Rebinding test.TestWidget.TestWidgetUiBinder
[INFO]                Invoking generator com.google.gwt.uibinder.rebind.UiBinderGenerator
[INFO]                   [ERROR] in {style.header}, no field named style: <div class='{style.header}'> (:14)
[INFO]          [ERROR] Errors in 'test/TestWidget.java'
[INFO]             [ERROR] Line 9: Failed to resolve 'test.TestWidget.TestWidgetUiBinder' via deferred binding
[INFO]          [WARN] For the following type(s), generated source was never committed (did you forget to call commit()?)
[INFO]             [WARN] test.TestWidget_TestWidgetUiBinderImpl
[INFO]          Unification traversed 625 fields and methods and 269 types. 1 are considered part of the current module and 9 had all of their fields and methods traversed.
[INFO]       [ERROR] Compiler returned false
[INFO]       [WARN] recompile failed
[INFO]       [WARN] continuing to serve previous version

Then when I remove the field="css", I still get the original get_clientBundleFieldNameUnlikelyToCollideWithUserSpecifiedFieldOkay_0_g error.

Java 21.
Windows 11 Home.

[jnehlmeier]

@craigmit Mhhh, then maybe I renamed the {style.xyz} as well so it compiles successfully. It is long ago that I had the issue the last time but I know I did change the field name to fix it. Or it is different with more recent GWT compiler.

[craigmit]

@craigmit Mhhh, then maybe I renamed the {style.xyz} as well so it compiles successfully. It is long ago that I had the issue the last time but I know I did change the field name to fix it. Or it is different with more recent GWT compiler.

Yep. That works:

1. Change header to be something else (eg: xyz).
2. Refresh page. Get same "FieldNameUnlikelyToCollide" error.
3. Change xyz back to header (or anything else). Works!