Comment 6 for bug 1631005

I can confirm the behavior that Jennifer reported in comment 5 - prior to the fix, the behavior for both fields defaulted to true if a value wasn't explicitly set, and after the change they defaulted to false.

I don't have a strong opinion on changing the default behavior or not, but if it were to change then it would need to be spelled out in the release notes and the setting description so that libraries doing upgrades would be aware of it.