> when clicking the active AirPods in the bluetooth list, there is a short 3~ second delay which makes you think they haven't been disconnected, leading you to

> when clicking the active AirPods in the bluetooth list, there is a short 3~ second delay which makes you think they haven't been disconnected, leading you to click it again. But your first click did actually fire leading you to be confused as to what state you are currently in. There is a known correct way to do this in UIs: no large delays for UI state change, even if the underlying function takes a humanly perceptible duration. Apple used to be good at this stuff, it's just attention to detail in UX... it's not like this is an area of opinion.