From: | Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com> |
---|---|
To: | Shruti B Iyer <siyer(at)pivotal(dot)io> |
Cc: | Robert Eckhardt <reckhardt(at)pivotal(dot)io>, Matthew Kleiman <mkleiman(at)pivotal(dot)io>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org> |
Subject: | Re: [pgAdmin4][PATCH] Improvements to Query Results Grid User Experience |
Date: | 2017-06-06 04:24:59 |
Message-ID: | CAM5-9D91pg6GjK8qA+r2yBUA-ziN24tkCK2N53_fGn21CWQaeg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Tue, Jun 6, 2017 at 12:13 AM, Shruti B Iyer <siyer(at)pivotal(dot)io> wrote:
> Hi Surinder,
>
> On Mon, Jun 5, 2017 at 2:09 PM Robert Eckhardt <reckhardt(at)pivotal(dot)io>
> wrote:
>
>> On Mon, Jun 5, 2017 at 9:09 AM, Surinder Kumar <
>> surinder(dot)kumar(at)enterprisedb(dot)com> wrote:
>>
>>> Hi Matthew,
>>>
>>> Couple of review comments:
>>> 1) Clicking on a new added row(after save) results in console error -
>>> screenshot attached.
>>>
>>
>>
> We tried to follow the steps you provided to replicate the bug but
> couldn't replicate the error. Can you provide further instructions to help
> us replicate the bug? Perhaps share a screen video if that makes sense.
> Is this occurring on the Edit Table view?
>
Sorry for wrong steps.
No need to add a new row, just double clicking on row selection column of
last row will throw that error.
>
> Thanks,
> Shruti and Matt
>
From | Date | Subject | |
---|---|---|---|
Next Message | Harshal Dhumal | 2017-06-06 06:42:09 | Re: Fix for RM2421 [pgAdmin4][patch] |
Previous Message | George Gelashvili | 2017-06-05 20:58:53 | Re: feature test timeouts |