Comment 8 for bug 1915282

Just following back up on this because it would be nice to have it figured out before the window closes on the Wallaby release, but also we're already nearly a month into the embargo... is there some consensus that this is an unlikely enough risk we could safely switch to discussing the bug and potential fixes in public instead?