SpeechSynthesisAnnouncer cannot be used before initialized

[jessegreenberg]

@marlitas I'm not sure what is happening, but with mac + safari when I try to set the second locale, the sim freezes with this error:

When using mac + chrome, I can add the second locale and didn't notice any speech synthesis bugs.

Originally posted by @Nancy-Salpepi in #152 (comment)

[marlitas]

I see this with Windows + firefox as well. Was working on #160 and got blocked by this.

[jessegreenberg]

This lazyLink is supposed to be preventing this exact issue from happening:

    // Voices may not be available on load or the list of voices may change - update if we get an indication that
    // the list of available voices has changed.
    this.voicesProperty.lazyLink( this.updateVoiceListener );

The voicesProperty changes in response to the onvoiceschanged event and on during initialization. I am guessing that we are hitting this while the SpeechSynthesisAnnouncer is being initialized. This may have been introduced in phetsims/utterance-queue#96 when voices became a Property.

[jessegreenberg]

OK, proposing the above commit to fix this. Instead of checking for populated voices we check to wait until the SpeechSynthesisAnnouncer has been initialized.

I am not sure when updateVoice needs to be called but if it has to be called on startup, you could also link it to the
SpeechSynthesisAnnouncer.isInitializedProperty as well.

EDIT:

if it has to be called on startup, you could also link it to the

That seemed right so I added it. @marlitas do you agree, anything else for this issue?

[pixelzoom]

Over in phetsims/number-suite-common#33, I reported that both number-play and number-compare are currently failing to start in Chrome when run from phetmarks. This is blocking further development and top priority. @chrisklus seems to think this issue is the cause.

[jessegreenberg]

Sorry about that! I guess I did not test phetsims/number-suite-common@3e1652f. Fixed with the above commit.

[marlitas]

@jessegreenberg this looks good, thanks for the work here! @chrisklus over to you for final review and closure.

[chrisklus]

Reviewed and discussed with @marlitas on Slack, changes look great and I tested on Safari and Chrome. Thanks @marlitas and @jessegreenberg! Closing.