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 implemented StorageEvents, and does so by eliminating it, bringing all browsers down to the lowest common denominator, and thenr replacing it with a similar behavior similuated within GWT.
But if I configure my GWT application to use StorageImpl for certain browsers with the configuration change described in this thread I can then make full use of StorageEvents in browsers that support it, as long as I am conscious of different behavior in different browsers.
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment