2017 Jun 30, 3:01
Previously I described Application Content URI Rules (ACUR) parsing and ACUR ordering. This post describes what you get from putting a URI in ACUR.
URIs in the ACUR gain the following which is otherwise unavailable:
- Geoloc API usage
- Audio and video capture API usage
- Pointer lock API usage
- Web notifications API usage
- IndexedDB API usage
- Clipboard API usage
- window.external.notify access from within webview
- window.close the primary window
- Top level navigation in the primary window
- Cross origin XHR and fetch to ms-appx(-web) scheme URIs
- Cross origin dirtied canvas read access if dirtied by ms-appx(-web) scheme URIs
- Cross origin text track for video element for tracks from ms-appx(-web) scheme URIs
URIs in the ACUR that also have full WinRT access additionally gain the following:
- Cross origin XHR and fetch
- Cross origin dirtied canvas read access
- Cross origin text track for video element
- Local audio and video WinRT plugins work with media elements
application-content-uri-rules coding javascript programming windows-store