Description
When using the Rhythm Ruler widget, if a user attempts to dissect a note cell into a subdivision that exceeds the maximum limit (256), the application fails to display the intended error notification and instead throws an uncaught TypeError in the console. This happens because the code attempts to call this.activity.logo.errorMsg, but the correct API for displaying UI alerts is this.activity.errorMsg.
Expected Behavior
The application should gracefully catch the invalid input and display a visible UI notification banner stating "Maximum value of 256 has been exceeded." without crashing the execution context or throwing console errors.
Screenshots
How to Reproduce
- Open the Music Blocks web application.
- Open the Rhythm Ruler widget.
- Rapidly dissect a cell (e.g., using the pie chart options) until the resulting
inputNum * noteValue exceeds 256.
- Observe that no visual error message appears on the screen.
- Check the browser console to see the
TypeError.
Environment:
- Operating System: Any
- Browser (if applicable): Any
- Version of Software/Project: master
Checklist
Description
When using the Rhythm Ruler widget, if a user attempts to dissect a note cell into a subdivision that exceeds the maximum limit (256), the application fails to display the intended error notification and instead throws an uncaught
TypeErrorin the console. This happens because the code attempts to callthis.activity.logo.errorMsg, but the correct API for displaying UI alerts isthis.activity.errorMsg.Expected Behavior
The application should gracefully catch the invalid input and display a visible UI notification banner stating "Maximum value of 256 has been exceeded." without crashing the execution context or throwing console errors.
Screenshots
How to Reproduce
inputNum * noteValueexceeds256.TypeError.Environment:
Checklist