Update implementation status with iOS Safari extension polyfill#670
Merged
Conversation
|
reillyeon marked as non substantive for IPR from ash-nazg. |
reillyeon
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the implementation-status document to note that Web Bluetooth can be polyfilled on iOS and iPadOS. It adds a reference under the Safari section for iOSWebBLE, a Safari extension that bridges navigator.bluetooth to CoreBluetooth through a SafariWebExtensionHandler process.
The text clarifies that this is a userland extension and not native WebKit support.
(Disclosure: I maintain the iOSWebBLE project. Please let me know if the wording or placement needs adjustment.)