forked from jquery-archive/jquery-mobile
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixed jquery-archive#2234 - form hijacking wasn't respecting allowCro…
…ssDomainPages, now it does!
- Loading branch information
1 parent
ff93c76
commit 88754ac
Showing
1 changed file
with
4 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 comment
on commit 88754ac
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes - I'm basically using the same functionality @jblas put in place under the click handler.
(Better comment here:
jquery-mobile/js/jquery.mobile.navigation.js
Line 1364 in 88754ac
// Some embedded browsers, like the web view in Phone Gap, allow cross-domain XHR |
Looks like this was originally set up in 2aab30b
I'd be definitely fine with making it wide open if allowCrossDomainPages is true, but I didn't want to do anything too dangerous, so I stuck with just bringing the clickhandler stuff over for forms. :)
I'm under the impression that the
allowCrossDomainPages
attribute was put in place to handle CORS requests but the variable name and the logical and operator seem to suggest that cross domain page loads are confined to those made with the file protocol. Was that the intention?