caniwebview: Legend of support table

[NiklasMerz]

Do we want to use the same naming as caniemail or our own names because we a have slightly different kind of data?

[aluhrs13]

Permissions might be a good case to think through how we want to communicate, since I don't think any webview is entirely green? I might be missing some APIs, but at a glance:

• Android can control Audio Capture, MIDI, Protected Media, and Video Capture through PermissionRequest, and location through GeolocationPermissions
• WKWebView has Audio+Video and Orientation+Motion.
• WebView2 has those and more for simpler allow/deny permissions, but not everything like the more complex UI shown when getDisplayMedia is called (open issue)

So should green mean some reasonable bar we want to set like Camera, Audio, and Geolocation? or 100% completeness for everything an app could do?

[NiklasMerz]

That's a great example. Possibly we need to define in the Feature description what "supported" or "supported with limitations" etc. mean for certain features. Consistency is critical here, too.

[NiklasMerz]

We are going for a simple legend now to avoid mixing support data & documentation status. Let me know if we should change it.