fix(tours): refresh the wanderer watch after a fixed token and truly disable its switch offline

The watch row only re-read its state when the connection came or went, so after
a passing connection test or a newly saved token it kept saying "Token refused"
until a reload. The connection card now hands it a key built from the saved
connection and its last check, and the row re-reads the watch whenever that
changes.

Without a connection the switch was only dimmed: the button stayed in the tab
order and was announced as active. ToggleSwitch gains a disabled prop that
disables the button and marks it aria-disabled, and the reason stays reachable
through a focusable wrapper carrying the tooltip.
This commit is contained in:
Maurice
2026-10-20 14:46:24 +02:00
parent 2e1dca9fe9
commit fbba4fd73b
8 changed files with 85 additions and 24 deletions
@@ -64,4 +64,26 @@ describe('ToggleSwitch', () => {
rerender(<ToggleSwitch on={true} onToggle={() => {}} />);
expect(button.querySelector('span')!.style.left).toBe('22px');
});
it('FE-COMP-TOGGLESWITCH-009: a disabled switch is out of reach and says so', async () => {
const user = userEvent.setup();
const onToggle = vi.fn();
render(<ToggleSwitch on={false} onToggle={onToggle} disabled />);
const button = screen.getByRole('button');
expect(button).toBeDisabled();
expect(button).toHaveAttribute('aria-disabled', 'true');
expect(button.style.cursor).toBe('not-allowed');
await user.click(button);
await user.tab();
expect(onToggle).not.toHaveBeenCalled();
expect(button).not.toHaveFocus();
});
it('FE-COMP-TOGGLESWITCH-010: an enabled switch keeps the pointer and no aria-disabled', () => {
render(<ToggleSwitch on={false} onToggle={() => {}} />);
const button = screen.getByRole('button');
expect(button).toBeEnabled();
expect(button).not.toHaveAttribute('aria-disabled');
expect(button.style.cursor).toBe('pointer');
});
});