Conversation
… of sayAllHandler
feerrenrut
approved these changes
Mar 11, 2021
feerrenrut
left a comment
Contributor
There was a problem hiding this comment.
Looks good! Thanks @seanbudd
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.
Link to issue number:
Part of #12123
Implements deprecation announced in: #10878
Summary of the issue:
sayAllHandler was changed to use
speakWithoutPausesas a default. Developers wanting to use the original behaviour ofspeech.speakTextInfowith reason as SAYALL should usesayAllHandlerDescription of how this pull request fixes the issue:
speakTextInfowill no longer send speech throughspeakWithoutPausesif reason isSAYAll, assayAllhandlerdoes this manually now.Testing strategy:
Search the code base for usages of
SAYALLand confirm the only ones that are being set are within sayAllHandler, which handles this behaviour and doesn't trigger deprecation warnings.Manual testing of "say all" behaviour - such as reading all the text or controls of a document may help confirm this and would trigger the deprecations warnings now if this wasn't handled correctly.
Known issues with pull request:
None
Change log entry:
Developer Changes
Code Review Checklist: