[ 
https://issues.apache.org/jira/browse/CB-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808714#comment-13808714
 ] 

Björn Andersson commented on CB-5219:
-------------------------------------

Looking at what the browser tells me it say it is IE Mobile 10.0, but amongst 
other things SVG:s doesn't work so it's something else than pure IE. But 
according to a [blog 
post|http://blogs.msdn.com/b/wsdevsol/archive/2012/10/18/nine-things-you-need-to-know-about-webview.aspx]
 the WP8 WebView does not support HTML5, whatever that means. 

As far as I know I got nothing that reloads the page, I'm using a framework 
called 
[Lavaca|https://github.com/mutualmobile/lavaca/blob/master/src/js/lavaca/net/History.js#L168]
 and I haven't seen anything to that effect along the way.

Also I tried this with the bare [hello 
world|https://github.com/apache/cordova-app-hello-world] project, adding the 
include for weinre and then adding in the line above. It also reproduces if I 
just add in weinre and then when connected to the device try to do replaceState.

> weinre disconnects when history.replaceState is used
> ----------------------------------------------------
>
>                 Key: CB-5219
>                 URL: https://issues.apache.org/jira/browse/CB-5219
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: WP8
>    Affects Versions: 3.1.0
>         Environment: Windows 8, Visual Studio 2012
>            Reporter: Björn Andersson
>            Assignee: Patrick Mueller
>
> I got an app that uses weinre and when developing on Android, BB10 and iOS I 
> never had any issues. But on WP8 it kept disconnect pretty much instantly 
> after connecting.
> I found that if I do:
> {code}
> history.replaceState(null, 'weinre, say bye-bye', '/some-fake-url')
> {code}
> Weinre will disconnect. I've tried this with the Cordova hello world app and 
> just adding in that line above disconnects weinre.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to