Thread: F5 - irritating behaviour
On Debian in Firefox If I terminate a running query, change it and press F5 again, a notification jumps up asking me whether I want to leave the page! Then I have to use the mouse to activate the query again. I am not actually sure whether it is always after a query was terminated that this happens. I am just getting a bit fed-up with this behaviour. Is there a way to get Ctl-E back as it was on pgadmin3? Regards Johann -- Johann Spies Telefoon: 021-808 4699 Databestuurder / Data manager Faks: 021-883 3691 Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie Centre for Research on Evaluation, Science and Technology Universiteit Stellenbosch. The integrity and confidentiality of this email is governed by these terms / Hierdie terme bepaal die integriteit en vertroulikheidvan hierdie epos. http://www.sun.ac.za/emaildisclaimer
On Thu, Nov 2, 2017 at 9:35 AM, Johann Spies <jspies@sun.ac.za> wrote:
On Debian in Firefox
If I terminate a running query, change it and press F5 again, a
notification jumps up asking me whether I want to leave the page!
Then I have to use the mouse to activate the query again.
It sounds like Firefox is grabbing the keypress. That shouldn't happen as long as the query tool has focus. Is that the case?
I am not actually sure whether it is always after a query was terminated
that this happens. I am just getting a bit fed-up with this behaviour.
Is there a way to get Ctl-E back as it was on pgadmin3?
I honestly had no idea Ctrl+E worked in pgAdmin III. The documented key was F5 there too.
We are looking into the idea of making shortcut keys configurable, so that may solve this.
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Thu, Nov 02, 2017 at 09:44:27AM +0000, Dave Page wrote: > On Thu, Nov 2, 2017 at 9:35 AM, Johann Spies <jspies@sun.ac.za> wrote: > > > It sounds like Firefox is grabbing the keypress. That shouldn't happen as > long as the query tool has focus. Is that the case? Yes. After editing the query (after terminating it) when I press F5... > We are looking into the idea of making shortcut keys configurable, so that > may solve this. Thanks. That will be useful. Regards Johann -- Johann Spies Telefoon: 021-808 4699 Databestuurder / Data manager Faks: 021-883 3691 Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie Centre for Research on Evaluation, Science and Technology Universiteit Stellenbosch. The integrity and confidentiality of this email is governed by these terms / Hierdie terme bepaal die integriteit en vertroulikheidvan hierdie epos. http://www.sun.ac.za/emaildisclaimer
On Thu, Nov 2, 2017 at 10:44 AM, Dave Page <dpage@pgadmin.org> wrote:
On Thu, Nov 2, 2017 at 9:35 AM, Johann Spies <jspies@sun.ac.za> wrote:On Debian in Firefox
If I terminate a running query, change it and press F5 again, a
notification jumps up asking me whether I want to leave the page!
Then I have to use the mouse to activate the query again.It sounds like Firefox is grabbing the keypress. That shouldn't happen as long as the query tool has focus. Is that the case?
Arguably it is pgadmin that expects to grab it from Firefox :) It's actually pretty horrible in general that a website *can* hijack hotkeys from the browser. I have issues with this all the time in other web systems (haven't really had a problem with pgadmin, but it's the same general thing) given that some hotkeys are different in different locales and the developers didn't consider that.
I am not actually sure whether it is always after a query was terminated
that this happens. I am just getting a bit fed-up with this behaviour.
Is there a way to get Ctl-E back as it was on pgadmin3?I honestly had no idea Ctrl+E worked in pgAdmin III. The documented key was F5 there too.
I used Ctrl-E all the time :)
We are looking into the idea of making shortcut keys configurable, so that may solve this.
That would indeed be great, and would solve the more general case I mentioned above as well (which I'm sure hurts somebody in some locale already).
//Magnus
I've always used F5 to the point that's a reflex. I use pgAdmin4 in a browser, usually Chrome, in server mode and about half the time F5 does what I want (executes the query) and the other half the time it tries to reload the page. It's annoying and I haven't figured out what triggers it. Philosophically I agree with Magnus Hagander's comment that it's horrible that a website can hijack hotkeys from the browser, but in this case I'm happy to put philosophy aside and get my F5 key back to reliably executing queries.
Rich
On Thu, Nov 2, 2017 at 7:34 AM, Magnus Hagander <magnus@hagander.net> wrote:
On Thu, Nov 2, 2017 at 10:44 AM, Dave Page <dpage@pgadmin.org> wrote:On Thu, Nov 2, 2017 at 9:35 AM, Johann Spies <jspies@sun.ac.za> wrote:On Debian in Firefox
If I terminate a running query, change it and press F5 again, a
notification jumps up asking me whether I want to leave the page!
Then I have to use the mouse to activate the query again.It sounds like Firefox is grabbing the keypress. That shouldn't happen as long as the query tool has focus. Is that the case?Arguably it is pgadmin that expects to grab it from Firefox :) It's actually pretty horrible in general that a website *can* hijack hotkeys from the browser. I have issues with this all the time in other web systems (haven't really had a problem with pgadmin, but it's the same general thing) given that some hotkeys are different in different locales and the developers didn't consider that.I am not actually sure whether it is always after a query was terminated
that this happens. I am just getting a bit fed-up with this behaviour.
Is there a way to get Ctl-E back as it was on pgadmin3?I honestly had no idea Ctrl+E worked in pgAdmin III. The documented key was F5 there too.I used Ctrl-E all the time :)We are looking into the idea of making shortcut keys configurable, so that may solve this.That would indeed be great, and would solve the more general case I mentioned above as well (which I'm sure hurts somebody in some locale already).//Magnus
Richard W. Greenwood, PLS
www.greenwoodmap.com
www.greenwoodmap.com