The support widget answers again, and typed times stay put

The support widget was dropping replies it had already written

On a public page, the assistant's answer streams into the widget as it gets written. The browser's security policy only listed the first connection the app was configured with, and that stream arrives over a different one, so the browser refused the request. The visitor read "Couldn't reach the assistant." while the answer sat there unsent.

Every origin the app is already configured to talk to is now on that list, so the reply lands. No new third-party origin was permitted.

Times you type into a date field now stay typed

A browser time input reports each piece separately: the hour, then the minute, then AM or PM. Each of those was being saved on its own, so the field kept snapping back to the stored value while you were still halfway through typing.

Start and End now hold a draft while you type and commit it once, a moment after your last keystroke, when you click away, or when the picker closes. The fields stay editable through the save instead of going read-only on you.

A couple of sequences used to lose an edit and no longer do. Type a time, click a calendar day right after it, and you keep both rather than the day overwriting the time. Clear a half-typed time and click away, and the stored value comes back instead of the date emptying out.

Under the hood

Date values are stored exactly as before, so cards, customers, and pages read and write unchanged. The picker writes once per finished entry instead of once per segment. Package versions are aligned to 2.2.5. Nothing here needs a migration, a new secret, or a feature-flag change.