Comment 8 for bug 1556045

seems what was happening was that the test was overriding the shell without syncing well enough with the Policy, resulting in racy raise behavior, that would toggle the visibility bit either one too many, or one too few times. The policy would only interfere as a result of SurfaceReadyBehavior, so it was rare.