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.

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

MS Edge: Cursor not defaulting to end of line #489

Closed
bolero3232 opened this issue May 11, 2016 · 7 comments
Closed

MS Edge: Cursor not defaulting to end of line #489

bolero3232 opened this issue May 11, 2016 · 7 comments

Comments

@bolero3232
Copy link

With IE, I just get a green map. With Microsoft Edge, it runs, but the cursor is at the far left instead of to the right. Also, it freezes in Edge.

@erikquinn
Copy link
Collaborator

Yeah, there's a bug with Internet Explorer that came up recently, it is being investigated in #477, and we have a lead on fixing it. Hopefully it'll be working again soon!

@bolero3232
Copy link
Author

bolero3232 commented May 11, 2016

What about the issue with Edge? Cursor comes up at the beginning of the line and I have to tab it over.
BTW, thanks so much for the support. I know I can be a pain sometimes. lol

@erikquinn
Copy link
Collaborator

Oh, like before the callsign when you select an aircraft?

@bolero3232
Copy link
Author

all aircraft

@erikquinn erikquinn changed the title still very buggy MS Edge: Cursor not defaulting to end of line May 14, 2016
@erikquinn erikquinn added the bug label May 14, 2016
@bolero3232
Copy link
Author

Running fine with IE now.

@GlenBush
Copy link

GlenBush commented Jun 2, 2016

I seen this as well on win10 was annoying but not breaking the game.

@erikquinn
Copy link
Collaborator

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.

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

No branches or pull requests

3 participants