[Button] Is the 'type' prop really removed from ButtonBase?

According to the docs, ButtonBase no longer has a type prop (which had values submit, reset, and button). Is this a deliberate change, or a documentation bug?

I’m asking because I’m generating MUI bindings from the docs. ButtonBase props are inherited by many other components, so I don’t want to remove it unless it’s intended.

[eps1lon]

I don’t think we intended to remove it from the docs. Just that we don’t want to restrict it at runtime because this might cause false positives. We never had any reports about <Button component="a" dowload type="audio/ogg" /> but this doesn’t mean that there are none. The runtime warning could’ve prevented legitimate usage of other type values.

I think documenting the allowed types for the default case and then widening the allowed types at runtime to PropTypes.string is a good compromise. In the end html validators or other 3rd party tools are probably better suited for verifying the output.

[oliviertassinari]

@cmeeren I think that we should document the custom default prop (type="button" over type="submit"), it can be confusing when building forms otherwise (I fell into this trap in the past building forms with our button). See https://github.com/mui-org/material-ui/pull/21002#discussion_r423994251

Should we remove the custom default type value?