[mwc-textfield] breaks UI if `type` is set to 'submit', 'reset', 'button'

[yinonov]

Describe the bug the types values of 'submit', 'reset', 'button' will render the native input element as a button, therefore breaks the UI and place a button instead of the expected contenteditable input.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior The above mentioned types should be restricted / ignored or fallback to a default value and keep textfield as a contenteditable input.

Screenshots

[dfreedm]

Thanks for the bug report! Given that this looks obviously broken, and that there are probably very few use cases for submit, reset or button types, I think we can just add some documentation and Typescript type validation.

[yinonov]

Fair enough!

[schirrel]

@dfreedm do you think would be a good approach to throw an error when using these types? Once they are not int TextFieldType and are being used at type property: @property({type: String}) type: TextFieldType = 'text'; Or maybe at the renderInput return the mwc-button?

[asyncliz]

M3 now has explicit supported and unsupported text field types that are enforced with typescript