Comment 13 for bug 1354512

Yes, this falls in the "feature has potential security consequences" bucket. It can be fixed/improved in future versions, but is not really backport material (since you would be changing behavior that a lot of people may rely on). It feels like it falls in the "improve in future versions, maybe document confusing state in OSSN" category.