-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.type() error is inaccurately stating what can be typed into #1650
Comments
Due to the fact that the supported type elements could change per version of Cypress - the error message should not link to an outside doc and instead include a list of supported type elements. Ideally, this list should be generated from the actual options checked, so they should be sent to the error message and generated from there. |
@jennifer-shehane If this is open I can work on this one. I will update accordingly with changes. |
@bishwenduk029 The work has already been done for this feature if you have any feedback to give here: #1651 |
Released in |
Current behavior:
If you call
.type()
on an element that is not supported for typing, the error displays:Desired behavior:
This error message is inaccurate and has led to a lot of confusion for users on what
.type()
supports typing into. In actuality, we support typing into:body
andtextarea
elementstabindex
attributecontenteditable
attributeinput
elements with a definedtype
attribute of one of the following:The error message should be updated to just say that
.type() has been called on an unsupported element
and link to a doc that lists supported elements.The text was updated successfully, but these errors were encountered: