http://gwt-code-reviews.appspot.com/1621803/diff/1/user/src/com/google/gwt/typedarrays/client/DataView.java File user/src/com/google/gwt/typedarrays/client/DataView.java (right):
http://gwt-code-reviews.appspot.com/1621803/diff/1/user/src/com/google/gwt/typedarrays/client/DataView.java#newcode128 user/src/com/google/gwt/typedarrays/client/DataView.java:128: private static native boolean isSupportedRuntime() /*-{ On 2012/01/06 15:27:16, tbroyer wrote:
On 2012/01/06 14:01:03, Steffen Schäfer wrote: > On 2012/01/01 22:34:57, tbroyer wrote: > > Is there really a need for a distinct check besides TypedArray.isSupported()? > > AFAICT, only Chrome m7 and m8 supported "typed arrays" without
supporting
> > DataView, and those versions are no longer used on the web; or are
there
> mobile > > browsers out there with similar "partial support"? > > Yes, it's necessary. Mozilla is a little bit late with that
implementation:
> https://bugzilla.mozilla.org/show_bug.cgi?id=575688
Oh, OK then.
At least for DataView. But you had specific isSupported() for all
typed-array
types, is that needed at all?
There are 3 isSupported methods: - TypedArray -> the general check if the API is supported - DataView -> because of Firefox - Uint8ClampedArray -> Because of WebKit (https://bugs.webkit.org/show_bug.cgi?id=74455) I hope that makes it a little bit more clear. http://gwt-code-reviews.appspot.com/1621803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
