4.290.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.287.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.283.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.280.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.278.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.276.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.272.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.270.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.267.0

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

4.252.0

Summary

This PR fixes the "Respond to a Call" functionality that was broken after the KendoUI removal in commit RE1-T104.

Problem

When clicking "Responding" → "Respond to a Call" (issue #317):

• The screen would go dark (modal backdrop appeared)
• But no modal content was displayed

Root Cause

Commit RE1-T104 switched from Kendo UI Windows to Bootstrap modals but didn't add the required modal HTML structure:

• Kendo's kendoWindow() could auto-create the window on empty divs
• Bootstrap modals require actual HTML with .modal, .modal-dialog, .modal-content classes
• The empty <div id="respondToACallWindow"></div> had no modal structure

Fix

Added proper Bootstrap modal HTML structure for both:

• respondToACallWindow - for responding to calls
• respondToAStationWindow - for responding to stations

The modal bodies are empty initially; content is loaded dynamically via JavaScript when the modal opens.

Testing

• Modal structure now matches Bootstrap conventions (same pattern as confirmSetAllToStandbyModal in the same file)
• JavaScript handlers for show.bs.modal will now find .modal-body elements to load content into

Fixes #317