Thanks Thomas. I see w3c_vibration.js in the closure-compiler: https://github.com/google/closure-compiler/blob/master/externs/browser/w3c_vibration.js
So it looks like the Elemental2 build needs to be updated to use w3c_vibration.js. Issue raised: https://github.com/google/elemental2/issues/177 On Tuesday, 19 August 2025 at 10:33:03 pm UTC+10 Thomas Broyer wrote: > Elemental2 is generated from the Closure Library definitions (with some > overrides), so first Closure needs to be updated to include it, then > Elemental2 needs to pick up the changes (assuming they are in a file that > Elemental2 looks at; so sometimes Elemental2 build needs to be updated) > > On Friday, August 15, 2025 at 1:03:39 AM UTC+2 [email protected] > wrote: > >> The opening statement of Elemental2 says "*Elemental2 provides type >> checked access to all browser APIs for Java code.*" >> >> I went to use navigator.vibrate ( >> https://developer.mozilla.org/en-US/docs/Web/API/Navigator/vibrate ) and >> found Elemental2 doesn't have it. >> >> Does anyone know why it's not there? >> >> -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/d572e484-d79b-4011-8b6a-7a303f4c7f81n%40googlegroups.com.
