Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Issue with .type when maxlength property is not defined on input #217

Closed
galkn opened this issue Feb 11, 2020 · 1 comment
Closed

Issue with .type when maxlength property is not defined on input #217

galkn opened this issue Feb 11, 2020 · 1 comment

Comments

@galkn
Copy link

galkn commented Feb 11, 2020

It seems that when the maxlength property is not defined on an input component, JS returns a value of -1 for it, which causes computedText to be incorrect (specifically the last character is consistently missing). Wondering if anyone else has observed this behavior?
@Gpx
Copy link
Member

Gpx commented Feb 17, 2020

Can you provide a minimal reproducible example for this bug, please? That would help figure out the problem.
I'm going to close the issue meanwhile, feel free to comment

@Gpx Gpx closed this as completed Feb 17, 2020
@cbacon91 cbacon91 mentioned this issue Mar 21, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix:type no longer clips final character with negative maxlength
2 participants
@galkn @Gpx