On Fri, Sep 27, 2019 at 7:16 AM Nick Couchman <[email protected]> wrote:
> On Fri, Sep 27, 2019 at 4:37 AM Vieri <[email protected]> wrote: > >> >> >> On Friday, September 27, 2019, 3:37:56 AM GMT+2, Nick Couchman < >> [email protected]> wrote: >> >> > I don't think this is possible just using a simple branding extension - >> you'd have to do some modifications to the login form itself in order to >> > affect this change. >> >> Right. However, I'm having trouble understanding how that can be done. I >> tried adding javascript code to the login page to try to disable the enter >> key, but it doesn't seem to work (not sure how to debug it). I understand >> Guacamole uses AngularJS. I'm not used to it so I'll have to read some more >> about that. >> >> > Yeah, off the top of my head I don't know - I would have to try a few > things to see what would work. I suspect that you need to intercept the > keyboard keystrokes, check for the Enter key, and then use an > event.preventdefault() to keep the keypress from being passed through. > Perhaps we should be invoking reset() on the Guacamole.Keyboard instance whenever there's a $routeChangeSuccess event? - Mike
