- From: Alex Rudenko via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Nov 2024 20:17:39 +0000
- To: public-web-bluetooth-log@w3.org
I too think that the current way the spec is written makes the most sense from test author/client perspective (i.e., configuring the simulated devices per top-level traversable). I think the Chromium implementation should follow that (if possible) but I do not think we need address this mismatch immediately. @reillyeon @alexnj do you know if there is an existing crbug to track aligning the CDP implementation with the specification? Although if it is really hard to achieve in the Chromium bluetooth implementation then perhaps we should consider changing the spec instead. > Current CDP implementation allows only a browser-wide "simulated Bluetooth adapter", while specification requires it to be browsing-context specific. Switching to navigable-specific will be a breaking change. I didn't get the "Switching to navigable-specific will be a breaking change." part? Is it a breaking change for the specification? I think it is already specified in terms of top-level traversables. -- GitHub Notification of comment by OrKoN Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/635#issuecomment-2486666091 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 November 2024 20:17:40 UTC