microsoft / microsoft/immersive-reader-sdk
Reader hangs when autoPlay and autoTranslation are both activated
Open
Nobody has claimed this yet.
bug
question
- Dominant language
- HTML
- Stars
- 110
- Forks
- 63
- Avg merge
- 6h 44m
- Merged PRs (30d)
- 21
Description
Steps to reproduce:
- launch ImmersiveReader with both readAloudOptions.autoplay = true and translationOptions.autoEnableDocumentTranslatio= true, plus a language that is different from the language of the input text chunk.
Expected result:
- document is translated into given target language first, then immediatly starts reading aloud.
Actual Result:
- Reader opens, translation of text is performed, but shows spinner instead of starting to read. Can't click on play.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by launching ImmersiveReader with readAloudOptions.autoplay and translationOptions.autoEnableDocumentTranslatio enabled, using a target language different from the input text. Trace the translation completion and autoplay flow; done means the document translates first, then reading aloud starts without a spinner and the play control works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100