Repository navigation
Document Web Bluetooth maximum write-without-response size - #46081
Draft
hjanuschka wants to merge 1 commit into
Draft
hjanuschka wants to merge 1 commit into
hjanuschka wants to merge 1 commit into
Conversation
Add reference pages for the connection payload limit and its change event, and link them from BluetoothRemoteGATTServer.
Contributor
|
Preview URLs (3 pages)
External URLs (2)URL:
URL:
|
This branch has not been deployed
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
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.
Summary
Add reference pages for
BluetoothRemoteGATTServer.maxWriteWithoutResponseSizeand itsmaxwritewithoutresponsesizechangedevent, including an example of chunking write-without-response data. Link both from the interface page.Status
Draft until the specification change and Chromium implementation land, and browser-compat-data has entries for the new property and event. The new pages link to the proposal directly and do not show compatibility tables yet.
ChromeStatus: https://chromestatus.com/feature/5177569273053184