On Tuesday, October 12, 2021 at 12:33:19 AM UTC+2 snianu wrote:
> Contact emails > > sni...@microsoft.com > > > Explainer > > https://github.com/WICG/keyboard-map/issues/38 > > > Specification > > https://wicg.github.io/keyboard-map/#permissions-policy > > > Summary > > getLayoutMap() used in conjunction with code solves the problem of > identifying the actual key pressed in keyboard with different layout maps > such as English vs French keyboards, but since getLayoutMap() isn't > available in all contexts (can't be used inside iframes), Office web apps > like Excel, Word, PowerPoint, etc. that show up as embedded experiences in > Outlook Web, Teams, etc. and are running in iframes, can't use this API. > Adding keyboard-map to the allow attribute list solves this problem. > Can you clarify what the current situation is? IIUC, currently layout maps are not available at all to iframes. Is that correct? Also, are you suggesting to add a permission policy that would enable it by default for same-origin iframes, and enable explicit delegation for cross-origin iframes? See this <https://github.com/WICG/keyboard-map/issues/38> Github issue for > more info. > > > Blink component > > Blink <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink> > > > Search tags > > keyboard-map <https://www.chromestatus.com/features#tags:keyboard-map>, > Keyboard <https://www.chromestatus.com/features#tags:Keyboard> > > > TAG review > > Not applicable as this is API has been shipped. > > > > TAG review status > > Not applicable > > > Risks > > Interoperability and Compatibility > > Currently Keyboard API is not supported on Safari and Firefox so interop > risk is minimal. Moreover, this proposal only allows the usage of the > Keyboard API inside an iframe if it's explicitly specified in the allow > attribute list by the web author. > > The feature policy names are based on the permission names, which have > been part of the permission policy spec > <https://w3c.github.io/webappsec-permissions-policy/>. > > > > *Gecko*: Negative (https://github.com/mozilla/standards-positions/pull/310 > ) > > *WebKit*: Negative ( > https://github.com/WICG/keyboard-map/issues/30#issue-487691188) > > *Web developers*: Positive ( > https://github.com/WICG/keyboard-map/issues/38#issue-934823530) > > Ergonomics > > None. > > Activation > > None. > > Security > > While there are fingerprinting concerns, this API has been shipped in > Chrome 69 and adding to the allow attribute list (like HID, > clipboard-read/write etc) allows sites like Office web apps to use this > API. The default value would be "self" (= top-level browsing context) but > sites could add it to allow list to access within iframe context. > > Debuggability > > The allow attribute has basic tooling support as described in this > <https://docs.google.com/document/d/1eJn5QIX4JFGackDYmdLxWXEmTDkSGj_ZGz5XY4uCKbY/edit> > > doc. > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ? > > Yes > > Requires code in //chrome? > > False > > > Tracking bug > > https://bugs.chromium.org/p/chromium/issues/detail?id=1258242 > > > Estimated milestones > > 97 > > Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/feature/5657965899022336 > > This intent message was generated by Chrome Platform Status > <https://www.chromestatus.com/>. > > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6f85e618-b193-4d67-ab06-e209d343385fn%40chromium.org.
