Sysapp Runtime: Allow-Navigation

Hi,



We would like to seek for clarification regarding chapter 7 of the runtime spec.



Use case example :



1. App-1 is a hosted app, with origin from www.myapp.com<http://www.myapp.com>.

2. In its manifest, it declares for permission to access Messaging and Raw Socket APIs.

3. In its manifest, it also declares to allow-navigation to www.myapp-service.com<http://www.myapp-service.com>.

4. Messaging API is used in : www.myapp.com/run1.html<http://www.myapp.com/run1.html>.

5. Raw Socket API is used in : www.myapp-service.com/run2.html<http://www.myapp-service.com/run2.html>.

6. User installed this App-1.

7. User executes this App-1.

8. User hits www.myapp.com/run1.html<http://www.myapp.com/run1.html> page, and messaging API access works fine.

9. User then hits www.myapp-service.com/run2.html<http://www.myapp-service.com/run2.html> page. Will Raw Socket API access works fine also here ?



10. Then finally, how if the App-1 above is actually a packaged-app ? Will the behavior be exactly the same ?



Thank You.



Best regards,

Darmawan.





http://www.w3.org/TR/2013/WD-runtime-20130321/



7. Navigation

Depending on the user interface around the application context, navigating outside the application's origin might lock the user out of the application.. To prevent that, the UA SHOULD NOT allow navigation out of the application's origin, unless the origin is specified in the following application manifest property:

* allow-navigation: the property SHOULD contain an array of origins that can be navigated to from the application.

If the application tries to navigate to an unauthorized origin, the UA SHOULD open the link in a regular but distinct browsing context.