From 89fc3d530bbf543c0ad1c3e019b964f9f557b19e Mon Sep 17 00:00:00 2001
From: Omar <fornanopods@gmail.com>
Date: Sun, 12 Jan 2014 22:20:07 +0100
Subject: [PATCH] Fixed initSelector as it works directly on widget.

Please note that the correct way to set a new initial selector `initSelector` is `$.mobile.widget.initSelector`. As `.initSelector` doesn't work with `.prototype`.
---
 includes/widget-option-initSelector.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/includes/widget-option-initSelector.xml b/includes/widget-option-initSelector.xml
index 0a6243cb..55f0625d 100644
--- a/includes/widget-option-initSelector.xml
+++ b/includes/widget-option-initSelector.xml
@@ -10,7 +10,7 @@
 			As of jQuery Mobile 1.4.0, the <code>initSelector</code> is no longer a widget option. Instead, it is declared directly on the widget prototype. Thus, you may specify a custom value by handling the <code>mobileinit</code> event and overwriting the <code>initSelector</code> on the prototype:</p>
 <pre><code>
 $( document ).on( "mobileinit", function() {
-	$.mobile.<placeholder name="name"/>.prototype.initSelector = "div.custom";
+	$.mobile.<placeholder name="name"/>.initSelector = "div.custom";
 });
 </code></pre>
 		</div>