On Sun, 6 Oct 2019 at 22:56, Jens wrote:
>
> Actually I believe it is a bug in closures externs from which elemental2
>> is generated. Without checking my guess is that IDBDatabase is annotated
>> with a @constructor tag rather than a @interface which is incorrect as
>> the spec defines it as an
Yes, the designer is all GWT using Lienzo; we have a few abstraction
layers, lowest is Lienzo followed by Stunner.
Regards,
Alex
On Sat, Oct 5, 2019 at 10:02 PM David wrote:
> Alex,
>
> Did you use GWT and Lienzo-core to build these new tools
>
> On Saturday, September 28, 2019 at 1:02:13 AM
> Actually I believe it is a bug in closures externs from which elemental2
> is generated. Without checking my guess is that IDBDatabase is annotated
> with a @constructor tag rather than a @interface which is incorrect as
> the spec defines it as an interface [1]. Unfortunately, this is a
On Sun, Oct 6, 2019 at 8:30 PM Thomas Broyer wrote:
> Wrt the cast error, it might be that the object in 'result' is not
> "instanceof $wnd.IDBDatabase". This would be a bug in Safari; and
> uncheckedCast is indeed the workaround.
>
Actually I believe it is a bug in closures externs from which
On Saturday, October 5, 2019 at 3:36:26 PM UTC+2, Shawn wrote:
>
> Hi,
>
> I get a ClassCastException under Safari, Safari on IOS and Chrome on IOS
> but not in Chrome.
>
Just a small note: all browsers on iOS are forced to use Safari's engine
(except IIRC they don't have access to some JS
