location.protocol problem

Develop and Deploy Native Apps for Windows, OS X, Linux, Unix ...

location.protocol problem

Postby joedarock » Thu Nov 03, 2016 1:10 pm

I have a comprehensive web app developed in CrossUI Ver 1.4 that I want to also deploy as a desktop app. The location.protocol property, which in Ver 1.3 and earlier used to return "file:" when deployed as desktop app, now returns "chrome extension" when deployed as desktop app. Any idea what's going on?
joedarock
 
Posts: 161
Joined: Thu Nov 19, 2015 8:39 pm

Re: location.protocol problem

Postby support » Fri Nov 04, 2016 2:11 am

We upgraded the nwjs version in CrossUI 1.4.

NW.js application is running as a Chrome App internally. All chrome.* platform APIs and features can be used in NW application now. The default protocol is changed from file:// to chrome-extension://, where the host part of the URL is the generated id. The app:// protocol in 0.12 is replaced by chrome-extension:// protocol.

http://docs.nwjs.io/en/latest/For%20Use ... to%200.13/
support
 
Posts: 350
Joined: Sat Apr 27, 2013 9:22 am


Return to CrossUI for Desktop Apps

Who is online

Users browsing this forum: No registered users and 0 guests