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

Lowercase m,k,- and some other keyboard keys stop working in the <input> element after opening and touching Google Maps - All platforms #415

Open
rbjarnason opened this issue Feb 21, 2018 · 3 comments

Comments

@rbjarnason
Copy link

After you open and touch a Google Maps using this components lowercase m,k,- and some other keys stop working in web input forms after opening and touching Google Maps.

Steps to reproduce:

  • Open a website with this Google Maps components (for example this one https://argyll-bute.yrpri.org/community/563 (select English top left and press MAP)
  • Press for example Login that has text inputs
  • Now lower cases m,k and some other keys wont work in any element

If you have the Google Maps form in the background you will actually see it move when use the keys but nothing comes into the input field.

This is a new problem since the new release of Google Maps on all platforms we have tested.

@rbjarnason rbjarnason changed the title Lowercase m,k,- and some other keyboard keys stop working in the <input> element after opening and touching Google Maps Lowercase m,k,- and some other keyboard keys stop working in the <input> element after opening and touching Google Maps - All platforms Feb 21, 2018
@rbjarnason
Copy link
Author

Here is more information about the same problem in a new Stackoverflow entry: https://stackoverflow.com/questions/48893262/google-maps-does-not-relinquish-key-presses-to-input-in-shadow-dom

@bungambohlah
Copy link

bungambohlah commented Apr 24, 2018

Hello @rbjarnason, same issue here..
and thank u for ur reference, it's very helpful for me, i've fixed my issue like this jsFiddle

@KeithHenry
Copy link

This is a bug in the underlying Maps API when in Shadow DOM: https://issuetracker.google.com/issues/73644075

The only workaround I've found is to disable keyboard keyboardShortcuts: false and re-implement them.

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

No branches or pull requests

3 participants