Status icon indicating copy to clipboard operation
Status copied to clipboard
verified publisher icon MicrosoftEdge

Add support for another ChromeStatus status

Open phistuck opened this issue 10 years ago • 3 comments

ChromeStatus has a new status - "In experimental framework". Currently, Web Bluetooth shows that Chrome does not support or develop support for it, but it does. https://dev.windows.com/en-us/microsoft-edge/platform/status/webbluetooth This is because of the new status, probably.

It would make sense to map it to "Preview release", I think, unless you want to add "Experimenting in Google Chrome" which is unclear.

Note that the Firefox platform status page maps it to "Developing" (but it also does so for "Preview release") - https://github.com/mozilla/platatus/blob/e0730d27d245b03cabe6b70bcbda9c2adecf1063/engine/index.js#L46

phistuck avatar Feb 05 '16 10:02 phistuck

I think this maps better to In Development than Preview Release. Things that are in Preview Release for Edge are generally near feature complete and are just waiting for a stable release train to ship, whereas Web Bluetooth requires special Chromium builds with flags and OS debug settings enabled, is not a full implementation of all the APIs, and only works with limited hardware.

jacobrossi avatar Feb 05 '16 22:02 jacobrossi

Mmm... not quite accurate.

  1. The "special Chromium build" (not special, really. Just a normal Chromium build, rather than a Chrome release) is required for Android 5 (Lollipop), which is not planned to be supported (the StackOverflow post mentions that). Even so, I also do not think it requires USB debugging (but off Google Play installations would probably be required). But this is irrelevant.
  2. Looks like all of the APIs are supported in Chrome 50.
  3. I am not sure the limited hardware situation is going to change a lot, unfortunately (but I do not know). I bet the limited operating system situation is going to change.

The experimental framework implemented by Chrome is supposed to be used to allow mostly (or even completely) ready features (that are included in specifications that are currently in flux) to let developers use them in production websites in a controlled manner. This, to me, maps to a preview release (but available by default only to authors that registered to use the API). But I do not feel strongly about it. :) As long as it does not show "Not supported" and the like, I would be pleased.

phistuck avatar Feb 05 '16 22:02 phistuck

I would appreciate if In Development was used there instead of Not supported for the Web Bluetooth API.

Please let me know where/if I can contribute to provide a patch.

cc @jacobrossi @nolanlawson

beaufortfrancois avatar Sep 29 '16 12:09 beaufortfrancois