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 1ugke2-006yz8-Ue for pgadmin-support@arkaria.postgresql.org; Tue, 29 Jul 2025 13:45:32 +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 1ugke2-001aqY-1X for pgadmin-support@arkaria.postgresql.org; Tue, 29 Jul 2025 13:45:30 +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 1ugXuN-00CIz9-8R for pgadmin-support@lists.postgresql.org; Tue, 29 Jul 2025 00:09:31 +0000 Received: from mail-43167.protonmail.ch ([185.70.43.167]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ugXuJ-001O37-1w for pgadmin-support@lists.postgresql.org; Tue, 29 Jul 2025 00:09:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1753747765; x=1754006965; bh=BQYfTzbZtdW6osphykPVFqEmxJUA+FNep11zIcUuBbY=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=NCjSjwdhBDugzmM6+MaW4c9uNOYRv+BkXG2s683R7PtfSnnFxI2zPxlWFj47bUo+9 kQHTOfpZ/VB5Obx4WTPUwc0TaxVORhLbsU8K0GoP1roZ4tL63u/nGxVpCPKodOhOKf xJJC/sBxdtGgFyCqQwCVmnw68xBe0QxURAQGsMJzcOBCHLa+wiE38fQcj3hDd31mKb jWvX2YXbgNE4L7r8bhB4ZRT/KWFBIEalSsKZPPvNj2ueJ8LkLVQPQO5zCmy53+b/yy 1RZzLNiTwT7I9TYsDhPszLQij6VGBjm9A/q/f06bhIhCOl/jx/osduJqg2/eVKcElF /m2JmdKMWcgYA== Date: Tue, 29 Jul 2025 00:09:21 +0000 To: "pgadmin-support@lists.postgresql.org" From: mullvadisen Subject: Will the hardcoded blinking cursor get an option to disable it soon? Message-ID: Feedback-ID: 65423556:user:proton X-Pm-Message-ID: 7b3198253ec6ce0679882b6d4723fb79bf7219da MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Three months ago, I sent an e-mail to this list about two serious annoyance= s which crippled my use of pgAdmin completely. One of them was that it had begun showing a white "flash" each time you ope= ned a new "page", before drawing the real (dark) background. This was lucki= ly fixed shortly afterwards. However, the second issue, the hardcoded blinking caret which doesn't respe= ct system settings nor has any preference to turn it off inside pgAdmin, re= mains. It looks like it has been added with "low" priority in a big list of= bugs/suggestions which I have no idea how long they will take for anyone t= o care: https://github.com/pgadmin-org/pgadmin4/issues/8712 (I had to ask s= omebody else to post it on Github because that site doesn't let me register= an account.) Since Mozilla and others has ignored important issues for decades, and I'm = literally screaming from frustration every time I'm using pgAdmin due to th= e blinking caret, I have to ask: is there any chance that this will be care= d about within a meaningful timeframe? I'm not exaggerating in the least wh= en I claim that at least to me, this is a critical bug which seriously prev= ents me from using the program. It really is that annoying. I always out of= necessity turn off blinking cursors and any other animated elements in my = computer environment, but it seems impossible for pgAdmin. Perhaps most of all I wonder how this can be something that only I seem to = care about. How are you all able to think and type in the SQL query or do a= nything else in the application when there's a blinking caret which constan= tly steals your focus and attention?