Geek Answers Handbook

Cordoba / UWP Windows Mobile 10 Violating Access to HTML Selection Element

In Visual Studio 2015 Update 3, I created a JavaScript -> Windows -> Windows 8 -> Windows Phone -> Blank App (Windows Phone) project JavaScript -> Windows -> Windows 8 -> Windows Phone -> Blank App (Windows Phone) . Then I changed default.html to include the <select> element:

 <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <title>App1</title> <!-- WinJS references --> <!-- At runtime, ui-themed.css resolves to ui-themed.theme-light.css or ui-themed.theme-dark.css based on the user's theme setting. This is part of the MRT resource loading functionality. --> <link href="/css/ui-themed.css" rel="stylesheet" /> <script src="//Microsoft.Phone.WinJS.2.1/js/base.js"></script> <script src="//Microsoft.Phone.WinJS.2.1/js/ui.js"></script> <!-- App1 references --> <link href="/css/default.css" rel="stylesheet" /> <script src="/js/default.js"></script> </head> <body class="phone"> <select> <option>Val</option> <option>Val</option> <option>Val</option> <option>Val</option> </select> </body> </html>

When you click on a selection item, the application crashes Windows Mobile 10 with:

 'WWAHost.exe' (Script): Loaded 'Script Code (MSAppHost/2.0)'. The program '[3976] WWAHost.exe' has exited with code -1073741819 (0xc0000005) 'Access violation'.

This happens on devices and the Windows Mobile 10 emulator. Windows Phone 8 does not seem to have this problem. Until recently, this worked fine on Windows Mobile 10. Perhaps the update caused this? Interestingly, Cordoba and UWP are also affected. Is the solution still known?

+7
javascript cordova uwp windows-10-mobile
source share
1 answer

I have the same problem. I have no fix, but I can at least explain what I found.

  • I tried using WinJS 2.1 and WinJS 4.4
  • The select element works great on Windows Phone 8.1 and Windows 10 (Desktop)
  • Edit # 1: Now I tried to do a full reset on my phone and install everything from scratch again - it would seem to pull in the last update when you do a reset - so that didn't help at all.
  • Edit # 3: I tried setting up all the different listeners (onclick, onchange, onmouseover, etc.) and none of them worked. Failure occurs before these events.
  • Edit # 3: I tried to completely reinstall the select element using CSS. Bad luck.

We both seemed to find this problem at about the same time. This would make me believe that this was caused by a recent update. I hope another update will be fixed soon.

I sent an email to MS support asking for more information, I will let you know if I find more. I tried to come up with alternatives to use instead of the select element, but I really could not find an easy solution. At least I will wait some time before I have to rewrite all my selected elements.

I know this does not help, but I will definitely update my answer if I find anything!

EDIT # 2: Here's the dump on the side right from the phone.

EDIT # 4: MS support mostly baffled me and told me to post a problem in my tech forums. Feel free to check out my post (hope to get more traction) or post your own thread.

EDIT # 5: I officially abandoned my job search. It is broken, and I (and no one who saw) was able to get around this problem. I had to replace all the elements in order to switch to a new screen using the ListView. It is frustrating that we have to reinvent the wheel in order to achieve something so simple.

+2
source share

More articles:


All Articles