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
Control now unresponsive on Android #20
Comments
Can you give us a demo project to reproduce this? |
So this is very strange @jessejiang0214 I created a sample app and no problems. So I then decided to test TEditor in an existing project which was roughly the same size as the project i was having the issue in and the issue reproduced.
I ran the project in Xamarin Profiler and here is what happened when I ran TEditor in the app (Red Box highlights TEditor interaction) Apologies that I cannot attach the project I do have the test Application linked below however that seems to execute the Editor fine. |
@jessejiang0214 what are your thoughts? |
If the demo App caonnot reproduce, I guess most reason is Android memory issue, maybe Android raise a GC and this error comes. Maybe you can try increase Android heap size, or GC before use TEditor |
This is just to fix Uncaught IndexSizeError: Failed to execute 'getRangeAt' on 'Selection': 0 is not a valid index
**But the problem is bigger.
ZSSRichTextEditor.js i am not sure why but when you click on the editor this event triggers constantly like in inifnity loop. I will write here if i find a wat to fix this issue.
|
My guess that the problem come from here(i've added the sel.rangeCount check)
This should fix this bug:
|
Can you give me a project which can reproduce this issue? |
https://drive.google.com/open?id=1FBxLd_Ch3WBeybHx7mEMcygkGMG1l5hI<- proj |
I have been testing out your control and it worked fine in the beginning, however now on android it is unresponsive.
When I exit the app and check my output i see the same error spammed a couple of hundred times:
"Uncaught IndexSizeError: Failed to execute 'getRangeAt' on 'Selection': 0 is not a valid index.", source: http://www.xam-consulting.com/ (940)
The text was updated successfully, but these errors were encountered: