Metadata
- Source
- SJRK-331
- Type
- Bug
- Priority
- Major
- Status
- Closed
- Resolution
- Won't Do
- Assignee
- N/A
- Reporter
- Gregor Moss
- Created
2020-03-19T21:30:17.907-0400 - Updated
2020-07-27T16:02:54.714-0400 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Storytelling Tool UI
Description
The Orator component is not working in Edge 44 (pre-Chromium). The component loads, and the Play button turns into a Pause button as expected, but nothing else happens. No errors are reported in the browser console to indicate what may have gone wrong.
This does not seem to be a problem with the Orator Demo page, nor with older deployed versions of the Storytelling Tool. It's possible this is related to recent updates in Infusion regarding FLUID-6145 and FLUID-6148, which are used in the current version of the Storytelling Tool. Filing this as a ST bug rather than component, in case the issue lies in the tool rather than the framework.
To reproduce:
- Create a story and go to the Preview step, or publish it, or load a previously-published story
- Click the Play button on the Orator component
Expected:
The Orator will read the story aloud, highlighting words as it goes
Actual:
The Play button turns into a Pause button, but nothing else occurs.
Environments
Custom-built PC
Windows 10 Pro build 1903
Edge 44.18362.449.0
Comments
-
Justin Obara commented
2020-03-23T08:36:55.406-0400 @@Gregor Moss the Orator demo is included in the demos directory of Infusion. If you pull down the branches related to the FLUID-6145 and/or FLUID-6148 PRs, you should be able to test them in Edge.
-
Gregor Moss commented
2020-07-27T16:02:54.652-0400 @@Justin Obara has been working on this issue as part of SJRK-370 (now that we have error messages to work with), and came across some causes in Infusion proper that would explain this behaviour. These are captured in FLUID-6533 and FLUID-6535, the first of which has already been addressed in Infusion and will make its way into the Storytelling Tool at some point.
Beyond that, we are planning not to support pre-Chromium Edge in the future (affects versions 44.* and earlier), so this may not be resolved for affected versions.