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

Cursor jumps to start of text window in UmpleOnline #1409

Open
TimLethbridge opened this Issue Nov 12, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@TimLethbridge
Member

TimLethbridge commented Nov 12, 2018

While editing the text in UmpleOnline, the cursor suddenly jumps from where you are editing, to the first character position. This completely disrupts the ability to edit.

There are several paths to reproduce. For example, create graphically two classes, give them attributes, and then link with an association (graphically). Now go to the text pane, and add an attribute in one of the classes. Pause for 3 seconds or so. Suddenly the cursor jumps from where it was.

Long ago we had this issue and somehow it was fixed. But it has returned. I suggest using Docker to look back to see if it is present in some of the early images, and see if we can figure out when it was introduced.

I am marking this as a critical issue.

@pwang347

This comment has been minimized.

Contributor

pwang347 commented Nov 12, 2018

Interesting, I could consistently reproduce this on try.umple.org with the steps above while the old assets were being used (in chrome the old js files and style are cached -- so the tabs weren't showing up either). After clearing cache with ctrl + f5 on Windows, I could no longer reproduce this. Would it be okay if you verify that this is still reproducible for you after the cache refresh as well?

@TimLethbridge

This comment has been minimized.

Member

TimLethbridge commented Nov 13, 2018

yes, it might be the case that this was an issue due to old cached assets. It seems to have gone away for now. I will keep this issue for a while. If anyone sees another case, please report here, with reproduction steps. I will close the issue in a few weeks if all seems clear. It used to be a sporadic issue that would pop up every now and then!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment