From b952c4afa6af6860b74fd2537c3f95fb66323f50 Mon Sep 17 00:00:00 2001 From: mbhnyc Date: Sat, 28 Apr 2012 11:59:20 -0300 Subject: [PATCH 1/2] Adding documentation to alert users that Facebook's OAuth callback causes jQuery Mobile to stop parsing a page, as well as solution. --- docs/pages/page-navmodel.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/pages/page-navmodel.html b/docs/pages/page-navmodel.html index d267f826644..ded8a5a5ea0 100644 --- a/docs/pages/page-navmodel.html +++ b/docs/pages/page-navmodel.html @@ -138,6 +138,8 @@

Known limitations

  • When traveling back to a previously loaded jQuery Mobile document from an external or internal document with the push state plugin enabled, some browsers load and trigger the popstate event on the wrong document or for the wrong reasons (two edge cases recorded so far). If you are regularly linking to external documents and find the application behaving erratically try disabling pushstate support.

  • jQuery Mobile does not support query parameter passing to internal/embedded pages but there are two plugins that you can add to your project to support this feature. There is a lightweight page params plugin and a more fully featured jQuery Mobile router plugin for use with backbone.js or spine.js.

  • Since we use the URL hash to preserve Back button behavior, using page anchors to jump down to a position on the page isn't supported by using the traditional anchor link (#foo). Use the silentScroll method to scroll to a particular Y position without triggering scroll event listeners. You can pass in a yPos arguments to scroll to that Y location.

    • + +

  • Some external applications (notably Facebook's OAuth implementation) modify their response URL in such a way that interferes with jQuery Mobile. In particular, Facebook appends #_=_ to the end of the callback. Currently the best solution for this is to remove it from the location hash before jQuery Mobile loads using something like: if (window.location.hash == "#_=_") window.location.hash = ""; . jQuery Mobile can then process & enhance the page properly.

    • From 15f9b78b297e99f0bd80c5a870841a6442143333 Mon Sep 17 00:00:00 2001 From: mbhnyc Date: Sat, 28 Apr 2012 12:01:46 -0300 Subject: [PATCH 2/2] Typo fix. --- docs/pages/page-navmodel.html | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/pages/page-navmodel.html b/docs/pages/page-navmodel.html index ded8a5a5ea0..196fa9dd115 100644 --- a/docs/pages/page-navmodel.html +++ b/docs/pages/page-navmodel.html @@ -138,7 +138,6 @@

    Known limitations

  • When traveling back to a previously loaded jQuery Mobile document from an external or internal document with the push state plugin enabled, some browsers load and trigger the popstate event on the wrong document or for the wrong reasons (two edge cases recorded so far). If you are regularly linking to external documents and find the application behaving erratically try disabling pushstate support.

  • jQuery Mobile does not support query parameter passing to internal/embedded pages but there are two plugins that you can add to your project to support this feature. There is a lightweight page params plugin and a more fully featured jQuery Mobile router plugin for use with backbone.js or spine.js.

  • Since we use the URL hash to preserve Back button behavior, using page anchors to jump down to a position on the page isn't supported by using the traditional anchor link (#foo). Use the silentScroll method to scroll to a particular Y position without triggering scroll event listeners. You can pass in a yPos arguments to scroll to that Y location.

    • -

  • Some external applications (notably Facebook's OAuth implementation) modify their response URL in such a way that interferes with jQuery Mobile. In particular, Facebook appends #_=_ to the end of the callback. Currently the best solution for this is to remove it from the location hash before jQuery Mobile loads using something like: if (window.location.hash == "#_=_") window.location.hash = ""; . jQuery Mobile can then process & enhance the page properly.