Skip to content

Navigate: fixed error in warning text #290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

agcolom
Copy link
Member

@agcolom agcolom commented Mar 23, 2014

Fixes gh-289

@@ -4,7 +4,7 @@
<desc>Alter the url and track history. Works for browsers with and without the new history API.</desc>
<longdesc>
<p>The <code>$.mobile.navigate</code> method provides a uniform history manipulation API for browsers that support the new history API and those that don't (hashchange). It works in concert with the navigate event by storing and retrieving arbitrary data in association with a URL (much like <code>popState</code> and <code>replaceState</code>). When the user returns to a URL set by the navigate method the navigate event is triggered with the associated data.</p>
<p id="low-level" class="warning"><strong>Note:</strong> This method is a low-level utility which can be used on its own. If you use the jQuery Mobile navigation framework, you should not separately use this utility. Instead, you should use <a href="/pagecontainer/">pagecontainer</a> event handlers to influence the navigation process.</p>
<p id="low-level" class="warning"><strong>Note:</strong> This method is a low-level utility which can be used on its own. If you use the jQuery Mobile navigation framework, you should not separately use this utility. Instead, you should use <a href="/pagecontainer/">pagecontainer</a> methods to influence the navigation process.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of "influence the navigation process" can we change this to just navigate?

@agcolom
Copy link
Member Author

agcolom commented Apr 7, 2014

Checked with @arschmitz and we've decided to change the wording to 'navigate to another page'

@arschmitz
Copy link
Member

👍

@agcolom
Copy link
Member Author

agcolom commented Apr 27, 2014

@arschmitz Hi Alex, could you please check that I did the right thing here? And then should I squash and land? Thanks.

@arschmitz
Copy link
Member

looks good @agcolom you are all set to squash and push this 👍

@jaspermdegroot jaspermdegroot added this to the 1.4 milestone Jun 5, 2014
@agcolom agcolom closed this in bc3ce67 Jun 17, 2014
agcolom added a commit that referenced this pull request Jun 17, 2014
apsdehal pushed a commit that referenced this pull request Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

warning on navigate event is incorrect
4 participants