From 485fa8650ad89466104fcd3fe64f09d701708e7b Mon Sep 17 00:00:00 2001
From: Gabriel Schulhof <gabriel.schulhof@intel.com>
Date: Thu, 29 Jan 2015 02:04:35 +0200
Subject: [PATCH 1/2] Navigation: Clarify the circumstances of and data
 associated with pagebeforechange

Fixes gh-355
---
 entries/pagebeforechange.xml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/entries/pagebeforechange.xml b/entries/pagebeforechange.xml
index 9393907e..88fdeb02 100644
--- a/entries/pagebeforechange.xml
+++ b/entries/pagebeforechange.xml
@@ -5,7 +5,11 @@
 	<longdesc>
 		<p>When received with <code>data.toPage</code> set to a string, the event indicates that navigation is about to commence. The value stored in <code>data.toPage</code> is the URL of the page that will be loaded.</p>
 		<p>When received with <code>data.toPage</code> set to a jQuery object, the event indicates that the destination page has been loaded and navigation will continue.</p>
-		<p>During the handling of this event the browser's history has not yet changed.</p>
+		<p>If the page change cycle was initiated programmatically, and, instead of a URL a jQuery object containing a page was given, then the event will be triggered both times with <code>data.toPage</code> set to the jQuery object containing the destination page.</p>
+
+		<p>The <placeholder name="name"> event is triggered either by explicit navigation on the part of the user (e.g. by clicking on a link or by running code that results in a call to the pagecontainer <code>change()</code> method), or by implicit navigation caused by the user clicking the browser's "Back" or "Forward" buttons.</p>
+		<p>Explicit navigation results in both <placeholder name="name"> events being triggered before a new entry is added to the browser's navigation history.</p>
+		<p>Implicit navigation results in both <placeholder name="name"> events being triggered after the browser's navigation history has already been updated.</p>
 		<p>In addition to the <code>event</code> parameter, handlers of this event will receive a second parameter, <code>data</code>. The second parameter is an object containing the following properties:</p>
 			<ul>
 				<li><code>toPage</code> (object or string)

From 888c694370b2d056fa6fc7bd971ba3ed3f08843e Mon Sep 17 00:00:00 2001
From: Gabriel Schulhof <gabriel.schulhof@intel.com>
Date: Tue, 3 Feb 2015 13:36:41 +0200
Subject: [PATCH 2/2] Navigation: Touch up blurb

---
 entries/pagebeforechange.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/entries/pagebeforechange.xml b/entries/pagebeforechange.xml
index 88fdeb02..aac34368 100644
--- a/entries/pagebeforechange.xml
+++ b/entries/pagebeforechange.xml
@@ -9,7 +9,7 @@
 
 		<p>The <placeholder name="name"> event is triggered either by explicit navigation on the part of the user (e.g. by clicking on a link or by running code that results in a call to the pagecontainer <code>change()</code> method), or by implicit navigation caused by the user clicking the browser's "Back" or "Forward" buttons.</p>
 		<p>Explicit navigation results in both <placeholder name="name"> events being triggered before a new entry is added to the browser's navigation history.</p>
-		<p>Implicit navigation results in both <placeholder name="name"> events being triggered after the browser's navigation history has already been updated.</p>
+		<p>Implicit navigation results in both <placeholder name="name"> events being triggered after the browser's navigation history has been updated.</p>
 		<p>In addition to the <code>event</code> parameter, handlers of this event will receive a second parameter, <code>data</code>. The second parameter is an object containing the following properties:</p>
 			<ul>
 				<li><code>toPage</code> (object or string)