Hey there Neil! Good catch here; I just fired this up on my test install and I’m seeing the same thing. Oddly enough we had this as a bug in our pre-3.0 beta code, and we fixed it there, but it appears to be rearing its head once more.
I’ve got this logged in our central ticketing system, so we should have a fix deployed in an upcoming maintenance release for sure. Thanks again for the heads up and for your patience until then. If we can do anything else, please let me know.