Actually, it looks like another user here on Community reported the exact same behavior, and it appears to have been caused by an extension they had installed:
Do you have any installed at this time? If so, can you try disabling them and then test again?