| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Harshal Dhumal <harshal(dot)dhumal(at)enterprisedb(dot)com> |
| Cc: | Matthew Kleiman <mkleiman(at)pivotal(dot)io>, Joao De Almeida Pereira <jdealmeidapereira(at)pivotal(dot)io>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgadmin4][PATCH] Query History Arrow Navigation and Styling |
| Date: | 2017-07-21 10:53:14 |
| Message-ID: | CA+OCxoyHCmePmnAoaKxK3b_L+kit-9oKfj-4BNdXjuE4KKUjQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Fri, Jul 21, 2017 at 11:05 AM, Harshal Dhumal <
harshal(dot)dhumal(at)enterprisedb(dot)com> wrote:
> Hi,
>
> On Fri, Jul 21, 2017 at 2:24 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> Hi
>>
>> On Fri, Jul 21, 2017 at 9:38 AM, Harshal Dhumal <
>> harshal(dot)dhumal(at)enterprisedb(dot)com> wrote:
>>
>>> Hi,
>>>
>>> Currently if user clicks on empty white area below history entry then
>>> arrow navigation does not work.
>>> Attached patch fixes this issue.
>>>
>>
>> This fixes that problem, but stops it working if I *don't* click on the
>> white area first. We need both I think :-)
>>
> Yes we need both. Please find updated patch
>
Why all the changes to yarn.lock?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Eckhardt | 2017-07-21 10:55:04 | Re: [pgAdmin4][Patch]: Allow user to Comment/Uncomment code in query editor |
| Previous Message | pgAdmin 4 Jenkins | 2017-07-21 10:42:06 | Jenkins build is back to normal : pgadmin4-master-python27 #259 |