For future reference: * Firefox 147 didn't show this issue, because sync about:blank was not yet there. * Firefox 148.0.0 didn't work with the GWT RichTextArea, because sync about:blank was there but this compat hack was not. * Firefox 148.0.2 has the compat hack without a message to the console in dev tools and without a use counter, and the compat hack requires building the GWT app with the default linker options that put `GwtPotentialElementShim` in the global scope. * Firefox 149 and later look for `__gwt_activeModules` in the global scope instead (bug 2022476), so the compat hack should work with any GWT linking alternatives. There is a message to the console in dev tools and a use counter.
Bug 2020927 Comment 21 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For future reference: * Firefox 147 didn't show this issue, because sync about:blank was not yet there. * Firefox 148.0.0 didn't work with the GWT RichTextArea, because sync about:blank was there but this compat hack was not. * Firefox 148.0.2 has the compat hack without a message to the console in dev tools and without a use counter, and the compat hack requires building the GWT app with the default linker options that put `GwtPotentialElementShim` in the global scope. * Firefox 149 and later look for `__gwt_stylesLoaded` in the global scope instead (bug 2022476), so the compat hack should work with any GWT linking alternatives. There is a message to the console in dev tools and a use counter.