Have you seen https://gwt-review.googlesource.com/5356 ?
On Monday, November 11, 2013 5:25:26 PM UTC+1, Andy wrote:
For a while I've been planning to move our gwt-traction library over to
github. Over the weekend, I decided to start with RawHistory.
RawHistory is a module that I suspect few
No, I haven't. Thanks for the link!
From a quick glance at the code, it's use of location.hash and
encode/decode will likely still cause issues for us. Over the next few
days, I'll try to create a version of my demo that uses the new code.
It could be that my expectations are wrong, but I
FYI URL encoding:
http://blog.lunatech.com/2009/02/03/what-every-web-developer-must-know-about-
url-encoding
2013/11/12 Andy pula...@gmail.com
No, I haven't. Thanks for the link!
From a quick glance at the code, it's use of location.hash and
encode/decode will likely still cause issues for
That's a great reference. It doesn't really explain what I'm seeing, but
it's well written.
On Tuesday, November 12, 2013 8:18:10 AM UTC-5, Juan Pablo Gardella wrote:
FYI URL encoding:
http://blog.lunatech.com/2009/02/03/what-every-web-developer-must-know-about-
url-encoding
2013/11/12
I should have mentioned that the example I showed above was for Safari.
Firefox does something different:
A link for:
fun/()(amp;)(%26)(%2526)/(%23)/(+)(%2B)(%20)(%252B)(%2520)/%E7%A6%85
becomes:
Safari/Chrome: fun/()(amp;)(%26)(%26)/(#)/(+)(%2B)( )(%2B)(%20)/禅
Firefox:
For a while I've been planning to move our gwt-traction library over to
github. Over the weekend, I decided to start with RawHistory.
RawHistory is a module that I suspect few people are using. It used to have
a note at the bottom saying that someday I'd explain exactly what it did.
As part of
