Book now button becomes clickable after mouse hover, not after date select

Description
On the single booking product page, after selecting a date in the calendar, the “Book now / Jetzt buchen” button remains disabled.
The button only becomes enabled after moving the mouse over the element .mwb-mbfw-cart-page-data (or a related container).

If the user selects a date and does not move the mouse over that area, the button never becomes clickable.

Expected behaviour
The “Book now” button should become enabled immediately after a valid date is selected, without requiring any mouse hover or cursor movement.

Actual behaviour

• Date is successfully selected and stored.
• Required AJAX calls complete.
• Button stays disabled.
• Hovering or moving the mouse over .mwb-mbfw-cart-page-data triggers another JS handler.
• Only then does the button become enabled.

Technical findings

• The plugin fires admin-ajax.php requests with action
  mbfw_retrieve_booking_total_single_page.
• The logic that enables the “Book now” button appears to be bound to mouse events (mouseover, mouseenter, or similar) on .mwb-mbfw-cart-page-data.
• The same enabling logic is not triggered on calendar date selection (change, input, or datepicker select events).
• This creates a UX bug where keyboard-only users or touch users may never get an enabled button.

Why this is a problem

• Breaks expected UX flow.
• Not accessible (fails keyboard-only / screen reader flows).
• Causes confusion: user selects a date but cannot proceed unless they accidentally hover a specific element.

Suggested fix

• Move or duplicate the “enable Book now button” logic so it also runs on:
  • calendar date selection
  • input/change events of the booking date field
• The button state should be derived from booking validity, not from hover events.

Repro steps

1. Open a booking product.
2. Select a valid date.
3. Do not move the mouse over .mwb-mbfw-cart-page-data.
4. Observe that the “Book now” button remains disabled.
5. Move the mouse over .mwb-mbfw-cart-page-data.
6. Button becomes enabled.

The page I need help with: [log in to see the link]