I fired up 152.0a1 (from nightly), did my steps above, and could no longer reproduce the issue. So it does seem to be fixed!