Feature Request P2
Status Update
No update yet.
Comments
th...@gmail.com
This should be a fairly quick fix for G Suite, and not doing so will have detrimental implications for many of my script.google.com projects, as well as other peoples' I imagine.
Starred! Please do attend to this.
Starred! Please do attend to this.
re...@kollab.com
Please to fix. Need this too for a project. Thanks!
m-...@esm.co.jp
Please support `camera` too.
[Deleted User] <[Deleted User]>
Hi,
Starting from Google Chrome 64 we can not use geolocation feature in Google Application Script based add-ons and web apps due to Deprecating Permissions in Cross-Origin Iframes (https://goo.gl/EuHzyv ).
Could you please follow Chromium guidelineshttps://goo.gl/EuHzyv to implement allow="geolocation" feature for GAS sandboxFrame.
Or we have to rely on alternative (non-Chrome) browsers eliminating these restrictions to continue using Google Application Script based add-ons and web apps?
Thanks
Starting from Google Chrome 64 we can not use geolocation feature in Google Application Script based add-ons and web apps due to Deprecating Permissions in Cross-Origin Iframes (
Could you please follow Chromium guidelines
Or we have to rely on alternative (non-Chrome) browsers eliminating these restrictions to continue using Google Application Script based add-ons and web apps?
Thanks
am...@gmail.com
Yes, please! We definitely need it, or our geolocation-dependent apps won't function once the feature is deprecated. :)
[Deleted User] <[Deleted User]>
Please support 'microphone' as well!
jo...@google.com
Hello there!
I analyzed and simulated your request. After reading how this behaviour affects your developments I collected the information in a report. I just shared it with the team in charge of this operation. Thank you all for your collaboration.
Description
every call for geolocation from HtmlService based frame causes a warning in Chrome 61:
[Deprecation] getCurrentPosition and watchPosition usage in cross-origin iframes is deprecated and will be disabled in M63, around December 2017. To continue to use this feature, it must be enabled by the embedding document using Feature Policy, e.g. <iframe allow="geolocation" ...>. See
In order for a cross-origin frame to use these feature, the HtmlService based frame must specify a Feature Policy which enables the feature for the frame. For example, to enable geolocation in an iframe the developer should be able to specify the iframe mode in scope of HtmlService.XFrameOptionsMode.ALLOWALL.