[meta] [web-bluetooth] Align our GATT API with W3C spec

NEW
Unassigned

Status

Firefox OS
Bluetooth
2 years ago
6 months ago

People

(Reporter: jocelyn, Unassigned)

Tracking

(Depends on: 4 bugs)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
Our GATT API is different from current W3C spec [1] due to historic reasons.
This meta bug is for all bugs needed in order to align with W3C spec including the security review.

[1] https://webbluetoothcg.github.io/web-bluetooth/

Updated

a year ago
Depends on: 1238479

Updated

a year ago
Depends on: 1238492
(Reporter)

Updated

a year ago
Depends on: 1238825
(Reporter)

Updated

a year ago
Depends on: 1238826

Updated

a year ago
Depends on: 1238842

Updated

a year ago
Depends on: 1238845

Updated

a year ago
Depends on: 1238853
(Reporter)

Updated

a year ago
Summary: [meta] Align our GATT API with W3C spec → [meta] [web-bluetooth] Align our GATT API with W3C spec

Updated

a year ago
See Also: → bug 674737
Is this fxos only? Is work being continued on this? If so why?

We need a Gecko-wide Bluetooth solution so we can:

A. Remain competitive
B. Provide a platform for future connected devices projects

Comment 2

a year ago
Wilson,

FYI. We bluetooth team, as part of Taipei office, is no longer dedicated to CD anymore. We have no reserved resource for WebBluetooth API in Gecko unless there's formal request to Taipei from other team (e.g., CD).

(In reply to Wilson Page [:wilsonpage] from comment #1)
> Is this fxos only? Is work being continued on this? If so why?

1) Yes, fxos only, wrapped with build flag.
2) No, it's suspended for being considered low priority.

> We need a Gecko-wide Bluetooth solution so we can:
> 
> A. Remain competitive
> B. Provide a platform for future connected devices projects

I understand but we are not the decision maker:(
(In reply to Wilson Page [:wilsonpage] from comment #1)
> Is this fxos only? Is work being continued on this? If so why?
> 
> We need a Gecko-wide Bluetooth solution so we can:
> 
> A. Remain competitive
There are many people in Mozilla showing their security concern to W3C WebBluetooth API exposed to the web. And we're struggling to suspend WebBluetooth work.
> B. Provide a platform for future connected devices projects
It's clear that it's not platform team's focus this year. We've discussed with platform team about exposing WebBluetooth API, and this work has been considered low priority. AFAIK, servo team is also working on W3C WebBluetooth.
You need to log in before you can comment on or make changes to this bug.