A button's type has three keywords: submit, reset, and button. A missing or invalid value puts it in the Auto state, and an Auto button is a submit button unless it has command or commandfor (or is the button inside a customisable <select>). Submitting is the historical default, kept for compatibility. So:
<button>Save</button>in a form submits it.type="button"does nothing by default; use it for anything script handles.type="reset"restores every control to its default value.
The rule in practice: always write type.
Which form? A control's form owner is its nearest ancestor <form>, unless it has a form attribute, which names a form by id anywhere in the same document. That lets a button or input sit outside the form's markup, for example in a sticky footer. element.form returns the owner, and form.elements includes controls attached by form. Forms can't nest: the parser ignores a <form> start tag while another form is open.
Which action? Submit buttons (<button> and <input type="submit"> or "image") can override the form for the submissions they trigger: formaction, formmethod, formenctype, formtarget, and formnovalidate to skip validation. Combined with name and value, which are sent only for the button that was clicked, one form can offer "Save draft" and "Publish" with different endpoints and rules.
Two interactions with newer features follow from the Auto rule. A type-less button with popovertarget in a form is still a submit button, so it submits and the popover doesn't open. A type-less button with commandfor in a form does nothing at all: the standard returns early for Auto buttons that have a form owner.