Remove prefix claims for Web Speech API member subfeatures #7554
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
The members (attributes and methods) of the Web Speech API interfaces are not themselves prefixes, the usage is > new webkitSpeechRecognition().start() not the doubly prefixed > new webkitSpeechRecognition().webkitStart() There are also issues with prefixes on some of the interfaces themselves, and a lot of repetetive notes, but this commit is only about the member subfeatures.
github-actions
bot
added
the
data:api 🐇
jpmedley
approved these changes
Dec 3, 2020
foolip
added a commit
to foolip/browser-compat-data
that referenced
this pull request
Dec 4, 2020
The set of webkitSpeech* members on the global object are: - webkitSpeechGrammar - webkitSpeechGrammarList - webkitSpeechRecognition - webkitSpeechRecognitionError - webkitSpeechRecognitionEvent These 3 other SpeechRecognition* interfaces are instead decorated with [LegacyNoInterfaceObject] in Chromium source, which means their interfaces objects are not exposed at all. They don't have constructors, as they are accessed from the `SpeechRecognitionResultList` at `event.results` for a "result" event. So while use of prefixes is required to get to these APIs, they are not themselves prefixed. See also mdn#7554.
jpmedley
pushed a commit
that referenced
this pull request
Dec 4, 2020
The set of webkitSpeech* members on the global object are: - webkitSpeechGrammar - webkitSpeechGrammarList - webkitSpeechRecognition - webkitSpeechRecognitionError - webkitSpeechRecognitionEvent These 3 other SpeechRecognition* interfaces are instead decorated with [LegacyNoInterfaceObject] in Chromium source, which means their interfaces objects are not exposed at all. They don't have constructors, as they are accessed from the `SpeechRecognitionResultList` at `event.results` for a "result" event. So while use of prefixes is required to get to these APIs, they are not themselves prefixed. See also #7554.
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.
The members (attributes and methods) of the Web Speech API interfaces
are not themselves prefixes, the usage is
not the doubly prefixed
There are also issues with prefixes on some of the interfaces
themselves, and a lot of repetetive notes, but this commit is only about
the member subfeatures.