Oh no! I just checked a couple different builds and couldn't recreate the issue. Did you try restarting your browser?
