Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Listener order dependency with two UtteranceQueues sharing an Announcer

Open
#49 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
accessibility

Research direction

Reproduce the issue with two UtteranceQueues sharing one Announcer, keeping the first queue nonempty. Start by tracing how UtteranceQueues are stepped through the stepTimer listener order and how readyToSpeak is consumed; done means both queues can announce rather than the later queue being blocked indefinitely.

Written by the indexing model from the issue text.

Description

type:bug

If you share an Announcer between two UtteranceQueues and an UtteranceQueue doesn't empty it is is possible that the second UtteranceQueue will never get to announce because the Announcer is used up (never readyToSpeak ) by the first UtteranceQueue.

UtteranceQueues are stepped, and the order that they are stepped is determined by stepTimer listener order (i.e. order of UtteranceQueue creation). If the first UtteranceQueue in listener order always has Utterances, the second one may never speak.

Dominant language
TypeScript
Stars
1
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phetsims/utterance-queue

All issues in phetsims/utterance-queue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.