Thanks for highlighting this, we've updated the build to fix this rendering issue (was a change in browser rendering since original publishing)
