Re: Replacing StorageImpl with itself?

OK this is starting to make sense to me now. It sounds like defaulting to StorageImplNonNativeEvents is intended to avoid browser compatibility problems since some browsers have not fully

Replacing StorageImpl with itself?

This rule overrides the "built-in" one that replaces StorageImpl with StorageImplNonNativeEvents. It wouldn't be needed if that other rule hadn't existed. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

Replacing StorageImpl with itself?

hello - I am looking for some insight into what might be going on with the workaround to Wrong LocalStorage event fire #9205 , an issue raised about a year and a half ago. I have observed the behavior described in the issue. I have also followed