Re: Place token decoded on Firefox, but not Chrome

Would you mind trying 2.7.0-SNAPSHOT from https://oss.sonatype.org/content/repositories/google-snapshots/ Maven repository?

The History implementation has changed a bit since 2.6.* and the behavior might have changed.

In any case, would you mind filing an issue in the tracker? as it looks like we should try to add tests about roundtripping tokens that need escaping.

On Monday, August 4, 2014 9:52:21 PM UTC+2, Jay Hodgson wrote:

Using the MVP sample app (linked to from the MVP Activities and Places developer guide), I set up to use GWT 2.6.1.

Go to the Goodbye place address after launching:
http://127.0.0.1:8888/?gwt.codesvr=127.0.0.1:9997#GoodbyePlace:%2B

Here's the output in Chrome:

Good-bye, %2B

In Firefox:

Good-bye, +

Why is the fragment URL-decoded in FF, but not in Chrome?

(This is causes an error in our application email validation round-trip.)

--
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/d/optout.