Comment 8 for bug 1316822

The chain of events is a bit unpredictable, but I'm leaning towards issuing a nadvisory here, unless the change ends up not being backportable (for example, if we decide the proper way to fix this is to disable a previously-supported behavior)