Re: History getToken causing infinite 250ms Timer Fire events

On Wednesday, November 13, 2013 5:38:25 PM UTC+1, Samyem Tuladhar wrote:

Noticed this old thread and found that the current version of GWT still uses the timer. Is this still necessary for Chrome? Seems to be taking a lot of memory.

It's for compatibility with older versions of Safari (we don't support older versions of Chrome, given that it auto-updates). You should be able to easily switch to using onhashchange by adding a rebind rule to your gwt.xml:

<replace-with name="com.google.gwt.user.client.impl.HistoryImpl">

  <when-type-is name="com.google.gwt.user.client.impl.HistoryImpl" />

  <when-property-is name="user.agent" value="safari" />

</replace-with>

FYI, onhashchange will be used for every browser in GWT 3.0 (where support for IE6/7 will definitely be dropped)

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.