Good catch, I’m seeing the same things here. This is not intended, i.e. this is a bug, but not sure exactly where. Maybe in the release tarball distributed by Mozilla, or in the code that decides which page to display based on the environment. Would you mind filing a bug so that we can track and investigate the issue further? Thanks!