I'm not sure if I want this level of detail here - I don't think it matters very much what the parent type is when it's "form", and I especially don't think it's very important to say exactly which class you can find the code in. Thoughts?

But I am kind of ok with the note here :), I think because if you're looking at this type, you're already in a more "abstract" and advanced place (since you don't actually, knowingly use "form" directly).

I'm not sure either. But we should be consistent. If we remove this note, we should also remove the "Overriden option" label for theauto_initialize option as you suggested. Otherwise it may confuse people.

Yep, I'm cool with removingauto_initialize from "Overridden Options" as I mentioned below. Besides, I'm not sure if there is a real use case at all for even knowing this option exists, so we should give it as little attention as possible.

I'm fine with this. Thus, I removed its description.

I see that we already havebutton_auto_initialize.rst.inc. I know that technically, how this is set tofalse is different between a button and other fields, but is there a practical difference? If not, we should delete thebutton_auto_initialize.rst.inc and include this one.

Oh, and if I'm thinking about this correctly, then there's really no purpose of havingauto_initialize as an "Overridden option" on the button docs. Yes, technically it is overridden, but it seems in practice it's not (it's false on all non-root forms, which strangely, I think is done onForm::add, not inside a form type).

Well, the default value is different for both types. Of course, we can consolidate both by creating a general file where we put a sentence like "default value is false for the button type, true for all other types". But I'm not sure if that is as clear as the solution we already have.

But practically, it's false for everything except for the parent form (it's just that this is done inside theForm::add method, and not in a form type). So in practice, I would argue that this option should appear only on the "form" type and shouldn't appear anywhere else as an overridden option.