-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TTS Autoplay bug fix #55713
TTS Autoplay bug fix #55713
Conversation
* boilerplate * updates for level creation * fix bug * add to allthethings * fix test * fix allthethings
- Schoology requires payload to be in the body, rather than a URL query. Canvas also accepts the payload in the body Signed-off-by: Nick Lathe <nick.lathe@code.org>
…1y/iframe-has-title Fix Violations of and Reenable `jsx-a11y/iframe-has-title`
* CSV for avon grove accounts to be purged * Change column name
DTT (Staging > Test) [robo-dtt]
* uitest: any student can complete rubric-enabled level * create teacher-associated students
[AccHack] Add labels for a few select and textarea components
…nd to page width (#55412)
… to non-standalone (#55450) * Prevent levelbuilders from accidentally switching a standalone course to non-standalone * Reword new unit creation flow * Fix tooltip * fix * Fix ui test
[AccHack] add labels or aria-labels for a few more input fields
DTT (Staging > Test) [robo-dtt]
[AppLab] Fix PropTypes error in DataVisualizer
CanCanCan 3.5
Removing PWA experiment code
* add generic mutators to custom blocks * load invisible blocks onto hidden workspace
DTS (Levelbuilder > Staging) [robo-dts]
* Revert "Revert "move regional partner search to dashboard"" * Use asset_path instead of webpack_asset_path
* Add string for select student option * Add student selection drop down component (redux connected) * Add student and section dropdown selectors to rubric content tab on FAB * Add section drop down and lesson name header to settings tab for rubric redesign * Remove commented out code * Move student selector style to rubric css styles * Remove redundant rubricId parameter * Fix test for new parameters * Remove debugging console logs * Update tests to connect them to the redux store and look for student/ section dropdowns
* Add user controller for show UI refresh * Use table-v2 * Add user controller logic * Fix values * Simplify * Remove last reference
* add tile images * update start-codeorg.haml * add aria labels to resources buttons * create resources_for_educators.haml view * update link on pl resource tile * add success page strings * update /afe/success.haml
* correctly translate behavior names * use both scopes * remove duplicate call
…uctions Adding LTI section login instructions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had one question about the shared_consts and one suggestion for a new test. Overall I think the queue was a great idea. Nice thinking!
lib/cdo/shared_constants.rb
Outdated
@@ -642,6 +642,33 @@ module SharedConstants | |||
} | |||
).freeze | |||
|
|||
VOICES = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see there was a TODO where these constants originally were. Is there a reason why these are shared with Dashboard? If they're defined separately in Dashboard currently, then we should switch the references from wherever they are in Dashboard to shared_constants
.
@@ -3,7 +3,8 @@ import {mount} from 'enzyme'; | |||
import sinon from 'sinon'; | |||
import {setExternalGlobals} from '../../../util/testUtils'; | |||
import React from 'react'; | |||
import {StatelessInlineAudio} from '@cdo/apps/templates/instructions/InlineAudio'; | |||
import {UnconnectedInlineAudio as InlineAudio} from '@cdo/apps/templates/instructions/InlineAudio'; | |||
import {AudioQueue} from '@cdo/apps/templates/instructions/AudioQueue'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way we could add a test where multiple audio items are input, and the test ensures they are played sequentially? Or maybe a test that ensures that the AudioQueue component functions properly?
Creates a Queue for Inline Audio such as instructions and hints to prevent Text to speech audio from playing all at once.
Links
Testing Story
Changes made to
InlineAudioTest.js
to include theAudioQueue
context. All tests pass.PR Checklist: