changePage breaks when data hash contains parentheses/apostropes

[konklone]

The following causes a syntax error in alpha 4:

$.mobile.changePage({url: "index.html", data: {foo: "bar(baz)"}, type: "get"});

In Firefox 4, the error message in Firebug's console is:

"Syntax error, unrecognized expression: data-url='index.html?foo=bar(baz]')"

Attempts to change the page without the parentheses work fine, such as:

$.mobile.changePage({url: "index.html", data: {foo: "bar"}, type: "get"});

[mckamey]

Note: Apostrope/Single-Quote also break changePage.

Issues #1383, #1408, #1468 are related.

Issue #1468 describes a workaround.

[driftingly]

On my implementation it's only the closing parenthesis that is causes an error. I have a search from that will pass results to a search page. Queries for "Some search (more" work whereas queries for "Some search (more)" break pageChange.

[driftingly]

I was able to get my forms working by running replacements on the serialized data bound to form submit event using the suggestion here: #1468

My new data looks like:
var newData = $this.serialize().replace(''','%27').replace('(','%28').replace(')','%29');

I updated the data in the function: $( "form" ).live('submit', function( event ) {});

Hope that helps people having a similar problem.

[johnbender]

#2384

Additional discussion in that pull request on possible solutions (eg escaping the url).

[toddparker]

@johnbender - Is this still an open issue?

[johnbender]

@mrlyons

The pr didn't get merged for the reason cited in the pull request: we need to address this in a couple places by escaping the hashes.

[smjgithub]

I'm currently using jquery.mobile-1.1.0 and I am serving it locally so that I could apply the partial fix from #1383.

Is this fix or a more complete version of the fix likely to make it into any official patch so that I can go back to serving jquery.mobile remotely?

[jaspermdegroot]

Updated the topic of this ticket so it also mentions "apostropes".

[SixtoSaez]

Ran across this issue in a pretty common usage scenario that may justify raising the priority of this issue. Our app passes names and such in the query string of the href attribute of a tags (see sample page: http://pastebin.com/TKybiryG). The name values (i.e. o'reilly) can sometimes contain single quotes which are a valid query string characters. Typical URL encode functions do not escape this character to a % encoding.

[dpolivy]

This still seems to exist in 1.4.2, and I'm hitting it with apostrophes in my query string portion of the url. Is there any progress on incorporating @SixtoSaez's PR or providing another fix?