Re: History.newItem() and History.getToken() and encoding url fragment (Does not happen in FF)

2010-06-03 Thread Thomas Broyer
On 3 juin, 03:38, Sky myonceinalifet...@gmail.com wrote: History.newItem() and History.getToken() are supposed to encodeURIComponent and decodeURIComponent respectively. I looked into the implemented native methods and they sure appear to do that. However, in FF 3.5 the encoding does not

Re: History.newItem() and History.getToken() and encoding url fragment (Does not happen in FF)

2010-06-03 Thread Sky
You're right! It does give %20 when I copy it and paste it in another app. Thanks. On Jun 3, 9:35 am, Thomas Broyer t.bro...@gmail.com wrote: On 3 juin, 03:38, Sky myonceinalifet...@gmail.com wrote: History.newItem() and History.getToken() are supposed to encodeURIComponent and

History.newItem() and History.getToken() and encoding url fragment (Does not happen in FF)

2010-06-02 Thread Sky
History.newItem() and History.getToken() are supposed to encodeURIComponent and decodeURIComponent respectively. I looked into the implemented native methods and they sure appear to do that. However, in FF 3.5 the encoding does not happen. My browser URL shows normal spaces instead of %20. In