Fixed issue in URL parsing (#8650)

* Fixed issue in URL parsing

Fixed "Broken URL parsing" issue mentioned in issue #8640 [details: 1) empty username or password are allowed, 2) colon in password is allowed]

* Handle forward and back slashes identically

To avoid incorrect parsing of URL like `http://evil.domain\@good.domain/

* addendum to "Handle forward and back slashes identically"

One slash has been missed

Author: dryabov

js/navigation/path.js

@@ -57,7 +57,7 @@ $.mobile.path = path = {
 	//    [16]: ?msg=1234&type=unread
 	//    [17]: #msg-content
 	//
-	urlParseRE: /^\s*(((([^:\/#\?]+:)?(?:(\/\/)((?:(([^:@\/#\?]+)(?:\:([^:@\/#\?]+))?)@)?(([^:\/#\?\]\[]+|\[[^\/\]@#?]+\])(?:\:([0-9]+))?))?)?)?((\/?(?:[^\/\?#]+\/+)*)([^\?#]*)))?(\?[^#]+)?)(#.*)?/,
+	urlParseRE: /^\s*(((([^:\/\\#\?]+:)?(?:([\/\\]{2})((?:(([^:@\/\\#\?]*)(?:\:([^@\/\\#\?]*))?)@)?(([^:\/\\#\?\]\[]+|\[[^\/\\\]@#?]+\])(?:\:([0-9]+))?))?)?)?(([\/\\]?(?:[^\/\\\?#]+[\/\\]+)*)([^\?#]*)))?(\?[^#]+)?)(#.*)?/,
 
 	// Abstraction to address xss (Issue #4787) by removing the authority in
 	// browsers that auto-decode it. All references to location.href should be