[w3ctag/design-reviews] Feature policy for Keyboard API (Issue #685)

Braw mornin' TAG!

I'm requesting a TAG review of adding a feature policy for Keyboard API.

The Keyboard API has been shipped, and this change just adds a new feature policy so web authors can access it from same/cross origin iframes. We wanted to get TAG's opinion on this change. Here is a brief 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.

  - Explainer¹ (minimally containing user needs and example code): (https://wicg.github.io/keyboard-map/#permissions-policy).
  - User research: N/A
  - Security and Privacy self-review²: [https://wicg.github.io/keyboard-map/#security]
  - GitHub repo (if you prefer feedback filed there): https://github.com/wicg/keyboard-map/issues/

  - Primary contacts (and their relationship to the specification):
      - [Anupam Snigdha](https://github.com/snianu), Microsoft
  - Organization/project driving the design: Microsoft
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://www.chromestatus.com/feature/5657965899022336


Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): Editing WG
  - The group where standardization of this work is intended to be done ("unknown" if not known): Editing WG
  - Existing major pieces of multi-stakeholder review or discussion of this design:
  - Major unresolved issues with or opposition to this design:
  - This work is being funded by: Microsoft

You should also know that...
Here is an existing issue describing the problem:
https://github.com/WICG/keyboard-map/issues/38


We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify [snianu]



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/685