jQuery.param.fragment strange behavior about jquery-bbq

[cowboy]

I'm not sure what you're asking. Just like $.param.fragment( '/some/url.html', 'a=1' ) will try to merge fragment params "a=1" into url "/some/url.html" and return "/some/url.html#a=1", $.param.fragment( '', 'a=1' ) will try to merge fragment params "a=1" into url "" and return "#a=1".

And you probably shouldn't compare BBQ "params" fragments as strings, because in different browsers (since objects' property order is unsorted and not guaranteed) there's the possibility that the individual params could be encoded in different orders.

[vvo]

What i'm trying to explain is that .fragment have different behavior when you call it with no params :

if your url is http://google.com/#q=yes

$.param.fragment() return "q=yes" without the #

while $.param.fragment('', 'q=yes') will return #q=yes so i was thinking that the behavior was different.

[cowboy]

That's the expected behavior, the documentation for jQuery.param.fragment states that the method returns:

The parsed fragment (hash) string, with any leading “#” removed.

[cowboy]

I think I actually need to update the documentation for jQuery.param.fragment (build url) to indicate that it returns:

A URL with a urlencoded fragment (hash) in the format ‘#a=b&c=d&e=f’.

[vvo]

Ok thank you for your anwsers, this is now closed