Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qWrGM-004XKJ-9W for pgadmin-hackers@arkaria.postgresql.org; Fri, 18 Aug 2023 04:39:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qWrGJ-008Cq1-3F for pgadmin-hackers@arkaria.postgresql.org; Fri, 18 Aug 2023 04:39:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qWrGI-008Cpt-Qr for pgadmin-hackers@lists.postgresql.org; Fri, 18 Aug 2023 04:39:02 +0000 Received: from mail-pg1-x536.google.com ([2607:f8b0:4864:20::536]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qWrGA-000n77-RV for pgadmin-hackers@postgresql.org; Fri, 18 Aug 2023 04:39:02 +0000 Received: by mail-pg1-x536.google.com with SMTP id 41be03b00d2f7-564b326185bso395821a12.2 for ; Thu, 17 Aug 2023 21:38:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692333532; x=1692938332; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=aWHVSMgFHcp5YARIvtvrVpWxkVqO83KcPMriHITXGbM=; b=l07NgP2pjSkRkjKbmuv6lfthL/jqrhWoqIjiGGbx1g6WxvGLewcYalcqh7CrpglxH3 s9BLnD+tOGmn0YrXsjI6Z9sdOr2gYVEWKXyXLSW06obksZgw8rRlRa1Sd15EbPNqCoGy 6X7K3plhbJyN0Wf1VOLKi3G1v4BnW00YXIqVeR9+l2czG20HovN9ZPscD+ovYGr9IrUp Il2ql11Gkll26yfHzjcO3M4H09gKej2lMMC4DgkUoChLv886MHm+Nb6eNnelgIbljwFO 7+WuhzXB8X+q2iwEspRU1cCNEtWwAc5pzd+q5gRWJheJESLYGbJA58jY8RTaqVqnQm3A gqhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692333532; x=1692938332; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=aWHVSMgFHcp5YARIvtvrVpWxkVqO83KcPMriHITXGbM=; b=c5mdk9gmQYduXIjSNrfwdr2MIFp+ZJvxTKWB4C7Baxve2MmaG3QnUjlk5QEP0U8s2a uvTxmAEChRUyWaTl6QU0Cy5hvouatjnL0ft7BGDcSWRWG1iqAR/jDT8bt6lws/9PY1tQ b0p+AoyC6YAJywJKXXQSmEPYBEUKqyfi1NYU8mLhHSUDK6IvEJxE1Z9a+MWaT+6OkC35 liy773YHrvhHKkJgC9wDUa/MsjI7Th3DsSGLx60rhyAx/kpA9WZlrmiIVaJrBbUCRIwM 1gkSzwxF4VqnZRbVnSPE7UdImx/2OKdtd8CDCylj9wv6IltPV6Pg4c/zT/nBkRfIFApe uLeg== X-Gm-Message-State: AOJu0YwQgYJ5VF0jZSkk+jMgU1CHmDUv3Wk+GII9qtYxj4CmZ+ZxBT+w REYzqS3eZl/kX+Z14TeQZ/Pxek/BS9SbSUdfIUw= X-Google-Smtp-Source: AGHT+IFYRW3PPaoY+seVAtr6e29xSYlE2yND7SL/YpLJ2TtXUAE0jgc++VS1d+sf3vxKRtz07tRcjNvaeL9BVe5NwSA= X-Received: by 2002:a17:90b:3144:b0:268:a61:ba86 with SMTP id ip4-20020a17090b314400b002680a61ba86mr1347789pjb.16.1692333532490; Thu, 17 Aug 2023 21:38:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sahil Harpal Date: Fri, 18 Aug 2023 10:08:36 +0530 Message-ID: Subject: Re: Pgadmin4 System Stats Extension Design To: Khushboo Vashi Cc: pgadmin-hackers@postgresql.org Content-Type: multipart/alternative; boundary="0000000000000bb57806032b1b6e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000bb57806032b1b6e Content-Type: text/plain; charset="UTF-8" On Thu, 17 Aug 2023 at 17:57, Khushboo Vashi < khushboo.vashi@enterprisedb.com> wrote: > > - The Tooltip for graph points remains on the page. Please refer to > the below screenshot. > > Is this happening simply by moving the cursor within the graph area or when resizing the screen? For me, it's working fine if I move the cursor within the graph area, but I can also sometimes observe this glitch when I attempt to change the screen width and quickly move the cursor within the graph area. --0000000000000bb57806032b1b6e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=3D""
On Thu, 17 Aug 2023 at 17:57, Khushboo Vashi= <khushboo.vashi@ente= rprisedb.com> wrote:
  • The Tooltip for graph points remains = on the page. Please refer to the below screenshot.
=C2=A0
Is this happening simply by moving the cur= sor within the graph area or when resizing the screen?

For me, it= 9;s working fine if I move the cursor within the graph area, but I can also= sometimes observe this glitch when I attempt to change the screen width an= d quickly move the cursor within the graph area.
--0000000000000bb57806032b1b6e--