Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fY9uL-0002ju-3A for pgadmin-hackers@arkaria.postgresql.org; Wed, 27 Jun 2018 12:50:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fY9uJ-0008Mf-Px for pgadmin-hackers@arkaria.postgresql.org; Wed, 27 Jun 2018 12:50:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fY9tJ-0005ph-Li for pgadmin-hackers@lists.postgresql.org; Wed, 27 Jun 2018 12:49:45 +0000 Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fY9tE-0001kX-I5 for pgadmin-hackers@postgresql.org; Wed, 27 Jun 2018 12:49:44 +0000 Received: by mail-wr0-x236.google.com with SMTP id b8-v6so1925401wro.6 for ; Wed, 27 Jun 2018 05:49:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ugErsHiWUBX53dsmNr+blHCmBpg314iaB1ZyZXojMlY=; b=NKopdNHwFl/DZnpWPlukppk/AHW960L1lGL1TYr0I4yahA8z4MSQirU8ZF3tXj787z GcbRuGhgduSOJ3Zxe/UkhwwbYh8QspWawmRbvv2dBuNOwrj/c1moL5cOz0V/6zXVg3uy dBWllVGZm3iFWZaz0uKFqAqZw579ZiAgDmYlYmIgVzDuFy9mACqpJvB6baqT3NC0CKrg cOaEwgHPBCZu/SfNvlOzOcMP0TWSzNCici4lKBAVUJct6WwWxhs4mO3sgre9ODHe08jl s+2IMK4z6UdAQALv2oVeHuznElXw/f1nnOCXsz7BIfuPWzBlSNXwgLno0ZIEq2ElOcKk cVJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ugErsHiWUBX53dsmNr+blHCmBpg314iaB1ZyZXojMlY=; b=jKTWiSF9P5IgzU+GC0FD0KJRnT032pzEil0B/WLJTdndS4vjvG5LCk96CLnaWM25nt SyVF0y8ePrX3RIp4L3LVSbU5VMgk5hp4TwvqcenFZHdW3EfO+4U/ZeU+gF7gLQDtXSy9 0Fs3BWmVKfqOcA275dGSToF/o5hyPYTj1wHqnGxy+/6w7sdwcmcLQKhcNPVO/RzKObA+ EqQreFUmQyfqpY7b6iIS0qbJlW3+JoiMZgCr2ouSj1BjIkdJgCdVSIHpl4Pxp3ItcJ5H se1WGjDJKkJz3QcSVypvamnRgVIg54coo0xtUJ+9LqS1onZBfrMWwyuSoyZveme7jugA 9vLw== X-Gm-Message-State: APt69E2UV4CFQR9Z53UzYoISmFI/a8i66hyEEsYad3dIf6cpk9fsEOzu KqRBAlwdCfnY02C55OqRpFeS3UHBhjPyIILYXxA= X-Google-Smtp-Source: AAOMgpfPKgo9j2Vr7/Dc2o8+9oXezR1Snio+sChqGYqjLBWeuIeolFUIWZHhiVkpYtk7PsKOKRSLF1pynNsD5FLJA44= X-Received: by 2002:adf:f011:: with SMTP id j17-v6mr4857250wro.260.1530103779090; Wed, 27 Jun 2018 05:49:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Anthony DeBarros Date: Wed, 27 Jun 2018 08:49:02 -0400 Message-ID: Subject: Re: pgAdmin v3.1 candidate builds and source... To: Dave Page Cc: Syed Fahar Abbas , =?UTF-8?B?RGV2cmltIEfDnE5Ew5xa?= , pgadmin-hackers Content-Type: multipart/alternative; boundary="00000000000038eb18056f9f0c98" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000038eb18056f9f0c98 Content-Type: text/plain; charset="UTF-8" Just to briefly follow up here. I cleared cookies for 127.0.0.1 in Chrome (there were three that seemed related to pgAdmin), then relaunched, and now the nodes expand properly. So, all good. Must have just been something in my browser session. On Wed, Jun 27, 2018 at 4:25 AM Dave Page wrote: > > > On Tue, Jun 26, 2018 at 6:45 PM, Anthony DeBarros > wrote: > >> Just fyi, I pulled a copy of the macOS version of this build, and for >> some reason I cannot expand the Tables node in the tree on any of my >> databases even though there are tables present. Could just be me, but >> wanted to note. >> >> Using Chrome beta 68; macOS High Sierra; Postgres 9.6 >> > > Does it work with release version of Chrome (or Safari)? > > If you turn on the developer tools in the browser, do you see anything on > the console? > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > --00000000000038eb18056f9f0c98 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just to briefly follow up here. I cleared cookies for 127.= 0.0.1 in Chrome (there were three that seemed related to pgAdmin), then rel= aunched, and now the nodes expand properly. So, all good. Must have just be= en something in my browser session.


On Wed, Jun 27, 2018 at 4:25 AM Dave Page <= dpage@pgadmin.org> wrote:


On Tue, Jun 26, 2018 at 6:45 PM, Ant= hony DeBarros <adebarros@gmail.com> wrote:
Just fyi, I pulled a copy of the macOS = version of this build, and for some reason I cannot expand the Tables node = in the tree on any of my databases even though there are tables present. Co= uld just be me, but wanted to note.

Using Chrome beta 68= ; macOS High Sierra; Postgres 9.6

Does it work with release version of Chrome (or Safari)?

<= /div>
If you turn on the developer tools in the browser, do you see any= thing on the console?=C2=A0

--
D= ave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB U= K: http://www.ent= erprisedb.com
The Enterprise PostgreSQL Company
--00000000000038eb18056f9f0c98--