-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Regression in 1.0.0-rc.13
#22
Comments
@serkandurusoy, I've tried to reproduce this behaviour, but I couldn't. Also, I've checked the whole repository and there's no single warning (even no |
@radekmie here's a minimal reproduction repo https://github.com/serkandurusoy/uniforms-issue22-reproduction |
Great! I'll take care of this. |
This looks like an React bug itself - I've created an issue for that. |
@radekmie what about the normal text types? they, too have the cursor moving to the end problem! The strange thing is, the problem goes away when I revert to rc.12 what do you think about that? |
I've made |
Yeah I'm actually looking at it right now and trying something, I'll let you know in a minute |
@radekmie I just pushed an update to my repo and included two custom components (text and email) that does not have dynamic type definition, but it still behaves the same,
so it may not be related to #19 but a combination of the other changes with #19 the cursor jumping might be a clue here about where we set the state of the value/error of the component such that it receives a rerender probably! |
Please give me a minute and I'll try something even better, I'll base a custom component on rc.12! |
@radekmie please take a look at https://github.com/serkandurusoy/uniforms-issue22-reproduction/tree/rc12-with-dynamic-type this is basically rc.12 + #19 combined and excluding #17 changes dynamic type is not a problem |
Hmm, why did you remove this line: |
I now tried rc.14 but did not make a difference in terms of this problem. |
I've removed it, because now |
Yeah, that's what I thought but just wanted to make sure. This is now becoming a mystery! |
@radekmie I do confirm that this now solves this problem. thanks! |
@radekmie part of the problem (the log messages about invalid inputs seen in the screenshot) started appearing again after the recent updates rc.23 and react 15.2 |
Moved from #17:
The text was updated successfully, but these errors were encountered: