I mean the hardware backKey that can be trapped with a backKey handler
normally, but the browser widget takes it over. I don't mind if the user
wants to backtrack through the links they've visited, but when they get
to their entry point bad things happen; I can't remember exactly what
went wron
(Assuming you don't mean the backKey that leaves your app.)
This is eventually not possible from security reasons.
There are brute force javascript approaches that probably will
break as soon as libbrowser changes and have side effects.
Using "on browserNavigateBegin" will lead to an infinite loo
I need to catch the backKey in a browser widget on Android. There's a
backKey handler in the card script but it doesn't trigger when the
browser has focus, the browser automatically handles it. Is there a way
to catch that keypress?
--
Jacqueline Landman Gay | jac...@hyperactivesw.
