Remove bluetooth permission descriptor #24769
Merged
Conversation
This file contains 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
github-actions
bot
added
the
data:api 🐇
Merged
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
the data is added in #22525, notice the chrome status says permission policy, not permission descriptor
if trying in to test in console (latest stable chrome), a
TypeErrorwill reportin chromium source code, there is a
bluetoothitem, but it is comment, which means it is not support in real browser (and notice that when the item added in chromium/chromium@9e5d5b7#diff-8ca96e3c008c457658e681b87bade1fdf5e235e551a34c8959c79ef21a8b4489, it is already comment and no change happens after that)also, no related info found when viewing other permission-related source code files
the chromium bug also confident is not supported
so I think chromium never implement this feature
the status for chrome should be set to
false, and then no platform will support this feature, so it can be removedsee also the related content update at mdn/content#32533
Test results and supporting details
Related issues