The permission prompt shows the name of the app but not the
origin of the request (e.g., “Can TestApp use your location?”). This
does not affect native objects managed by Windows Runtime because
they are not visible to remote Web code, but it affects the
W3C geolocation API which is exposed to Web code by Windows.
If an internal application page requests access to the geolocation
object and the user approves, all third-party Web content included
in this app will implicitly get access to geolocation.