Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Flash player doesn't respond to some keyboard input after file save

  • 4 antwoorden
  • 1 heeft dit probleem
  • 4 weergaven
  • Laatste antwoord van richardmmap

more options

Firefox 61.0.1 (64-bit) Windows 10

After file save (see image below), Flash player no longer responds to some keyboard input. For instance, users can no longer press ctrl + c/ctrl + v to copy/paste within the Flash app. Neither can they press ctrl + click or shift + click to select multiple rows in a Flash data grid. I've tried forcing focus back to the Flash app using both js and actionscript with no result.

Prior to file save everything works as expected.

Any help would be greatly appreciated.

Thanks in advance

Firefox 61.0.1 (64-bit) Windows 10 After file save (see image below), Flash player no longer responds to some keyboard input. For instance, users can no longer press ctrl + c/ctrl + v to copy/paste within the Flash app. Neither can they press ctrl + click or shift + click to select multiple rows in a Flash data grid. I've tried forcing focus back to the Flash app using both js and actionscript with no result. Prior to file save everything works as expected. Any help would be greatly appreciated. Thanks in advance

Alle antwoorden (4)

more options

Does other browsers exhibit the same problem?

more options

WestEnd said

Does other browsers exhibit the same problem?

No, not in the browsers that I've tested. IE 11.165.17134.0 and Chrome 67.0.3396.99 (64-bit)

more options

Did you try to switch to another tab temporarily and then go back to the tab with the Flash game?

more options

cor-el said

Did you try to switch to another tab temporarily and then go back to the tab with the Flash game?

Yes, but this did not fix the problem.

Additionally, the app no longer completely loads when accessed from the web. It loads about 3/4 of the components then stops. The clock just keeps spinning...