parseUrl and makeUrlAbsolute incorrectly parse and generate URLs with the Windows 'res:' protocol.

[bbesseling]

In a Windows app where we want to use jqm as the user interface in an IWebBrowser2,
when the document base is the Windows app resource URL

res://device:\\directory\\file.exe/resource.html,

the function jQuery.mobile.path.parseUrl incorrectly parses the 'device' part (which could be e.g. 'C' or 'x-wmapp1')
into the authority, host and hostname fields.
This causes the function jQuery.mobile.path.makeUrlAbsolute to convert #two into

res://device/:\\directory\\file.exe/resource.html#two with a spurious '/' after device.

This causes all non data-ajax="false" navigation to fail

The res:/' protocol should also be treated like the file:/// protocol.
respathissue.zip

[apsdehal]

JQM is not supposed to work with file and res protocols.

[arschmitz]

we do support native file protocols for apps like this

[arschmitz]

I think we fixed this already though might just be for 1.5 @gabrielschulhof do you recall?

[gabrielschulhof]

Yeah, there was an issue with Cordova on Windows, but I don't remember if it made it into 1.4.x or not.

[gabrielschulhof]

#6574

[apsdehal]

I can reproduce the issue still with latest 1.5-dev, I don't think it is fixed yet.

[gabrielschulhof]

The original problem I think was that the res protocol has no absolute path. That is, it looks like this:

res:path/to/file.html

And so it's hard to correctly identify the path, because / is assumed to follow the protocol to indicate an absolute path.

[gabrielschulhof]

Is it possible that there's a regression in Cordova?

[gabrielschulhof]

@apsdehal can you please detail the steps you used to reproduce it with 1.5-dev?

[apsdehal]

@gabrielschulhof I reproduce it with URI given in the issue description, though I am not sure if this URI is correct. Can you confirm this?
$.mobile.path.makeUrlAbsolute("#two", "res://device:\\directory\\file.exe/resource.html")

[bbesseling]

yes, that is the URL from the original problem submission.