We may need to seperate it a bit more: As of 2.3, the form type is extracted in aFormType and aBaseType (not included in the form tree), theFormType extends theBaseType.
This is done, because the form buttons use theBaseType and not theFormType.

So we can't say, these options are available on every field. And we may need to make a difference between options of theBaseType and options of theFormType, in cases someone wants to create a custom button.

You're right. This also applies to theButtonType docs. But I'm not sure if it is a good idea to create separate docs for theBaseType and reference its options via ainherited options section sinceBaseType is no real form type that can be used.

No, I think we should split the Form Type article. Or add something like(BaseType) to the options used by the base type with a little explaination in the beginning why there is a difference betweenBaseType andFormType options.

We can go that way. But then the same should be documented for theButtonType. What do you think?

I added an additional table to theform type listing the options inherited from theBaseType class and added a note to thebutton type reference.

I also added docs for theauto_initialize option.

@xabbuh I think I'm happy with this now :). Can you rebase for me?

@weaverryan Of course, here you are.

Awesome, thank you very much!