Olivier, I don't mind the people who don't read the documentation who are then going to figure it out by trial and error.
I get bothered by the people that don't read the documentation and then post they've found a bug, and when we help them, ignore everything we've said because "it's a bug in the code". And then start writing inflammatory posts and sending the same via email to developers. This has happened four times since I've come on board. Twice with this forum being involved. But, thank the powers, those people have left.
Honestly, I could never figure out why they stuck around passed that first day anyway. So, I tend to be a bit defensive about this.
Further down in the post you quoted, I did mention that we should do it the FRUA way, since that is what we want to emulate. And FRUA always defaults to 'always'.
I don't count this as a high priority bug, so it probably won't be fixed in the next release, but it will definitely be fixed for version 1.0.
