--- Comment #45 from [hidden email] ---
(In reply to comment #41)
> I think this bug should just be closed as “resolved fixed,” since the
> current implementation addresses the originally reported issue. [...]
I agree with everything you said.
It should be closed as "fixed".
It should be properly documented.
It should be left "on" as default, like it is now.
It should not be moved to expert config.