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 1uh3Xv-00A3S2-RC for pgadmin-support@arkaria.postgresql.org; Wed, 30 Jul 2025 09:56:28 +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 1uh3Xu-008TL7-HO for pgadmin-support@arkaria.postgresql.org; Wed, 30 Jul 2025 09:56:26 +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 1uh3Xu-008TKz-8R for pgadmin-support@lists.postgresql.org; Wed, 30 Jul 2025 09:56:26 +0000 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uh3Xq-001e0G-0R for pgadmin-support@lists.postgresql.org; Wed, 30 Jul 2025 09:56:25 +0000 Received: by mail-lj1-x230.google.com with SMTP id 38308e7fff4ca-3321296a8cfso8276341fa.0 for ; Wed, 30 Jul 2025 02:56:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1753869380; x=1754474180; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=39LjaeyfcmaDweXlbDPJ884Ot12pooZi72c2umvMDjw=; b=DXfUIhy35vZx2W5U5WN+w9b2Ei5XHPFtibLLHhpLPfIjXXFPiIRpOWLxqkZOWAbIpS HYVYN7hoP3T430MG0i1jxe/1CCoyNLSMtnP6bJwZqTh+2s8OWCDoZvblSQ9f2urGkw3V RfeUksPUU1HEcnEqqjc344hUWUHxMJ9nFe4M5dTvkYsVpCESU9pozZwnxPudQH4Vnqb4 POBvzzuBrq67NT/ghYJ+aZrBtBAux4ubamVIOQE489zJejcroDGytza43j6FGcm96Dp2 yUWzDGijzB8a7OXUIY0zVuFQ2oQvuLqOf+YxzAlSG3wCYVPt9TQY+5k+BHCYcpVWQaHI JlSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753869380; x=1754474180; 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=39LjaeyfcmaDweXlbDPJ884Ot12pooZi72c2umvMDjw=; b=RwaJObjGzcjMCQB3AQ2lKvjGaz4l3MP4pJFuF7+cnNr94QgT0v+2u9wxXQhjrIfdDl zfbhl0cwQkjYhfz5Vi7k57eYniIn4OzuiJXrmgn+qwlYK4nShPA7R2HKNjflZAwFxI5j 8eNS0skCwp/dzXoZoeDZ018Lo2HTYgnWtCI0hs11LjXFz95cB61toCqrxkO1WidDUEVg MJF5rV9nuyBXT0RIQ0N4KczPErW7bgDMKZeY4s7//q36+XgfkOYRZWdNNhJYtL2YVyeG YOfwE0gRcCrAQzTgBL9yYXlREvfKF62ieP8p/mS9bMqMFrh/lW5tySP99RvRigjE2fcd t1cA== X-Gm-Message-State: AOJu0YxKAgvFDa6tyZeKIosxfQw4cUp5YPrVLNPtdFprGunKiPyxmxd1 Ft24P+XDJ40WHMY/Lh0fztUMbCRKL3FUTnhC68GxZYW3xaX1IggHB9SMLjdMKEPU03B/5gslX2a xvCasvyLA/bXBdy9CgSHoUu/AhXHgTULgHcVz30dT X-Gm-Gg: ASbGncsz5vB+gJAu9MhjJpxpqqoklcEi+NF04CV75FzqyB1HsOvhBYMDPPvKFJR92B8 uglTDBfXlnl+zbitMEqZfR1poycaZKA9EE3gscugJAnT8R3efogeGQ1Z8VyKojd9Ei685MkGuEf jwzNHpuhfObG2hnnLxpeAD3+KRAs7EHtx0VVLAuMR55kr+DVMehr/8RWnjGvvBHxeS8fTtKMImU hPbYpmNcwZ1XfgT+IuEoawljffeG+1fBF2oeiNp X-Google-Smtp-Source: AGHT+IEGZp+cCQyGNDuJAt28343vu/QhkErCXk5Anuara3keK379xeAFkswpE1Y/6QEsRNc/Xzue2ngT9TctUGjZt9I= X-Received: by 2002:a05:651c:e07:b0:32d:fd75:7bc0 with SMTP id 38308e7fff4ca-332154d6644mr13916071fa.20.1753869380043; Wed, 30 Jul 2025 02:56:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Akshay Joshi Date: Wed, 30 Jul 2025 15:26:08 +0530 X-Gm-Features: Ac12FXwSvtwIa75y_ya-VGqipH80e_UdFMDvy6tjPIU9GCEihocAyG5irEgMP2E Message-ID: Subject: Re: Will the hardcoded blinking cursor get an option to disable it soon? To: mullvadisen Cc: "pgadmin-support@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000061654f063b2289d3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000061654f063b2289d3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Mullvadisen, We have prioritized the issue and added it to the current sprint. It should be resolved in the next release (v9.7). We'll assess the feasibility and keep you updated. On Tue, Jul 29, 2025 at 7:13=E2=80=AFPM mullvadisen = wrote: > Three months ago, I sent an e-mail to this list about two serious > annoyances which crippled my use of pgAdmin completely. > > One of them was that it had begun showing a white "flash" each time you > opened a new "page", before drawing the real (dark) background. This was > luckily fixed shortly afterwards. > > However, the second issue, the hardcoded blinking caret which doesn't > respect system settings nor has any preference to turn it off inside > pgAdmin, remains. 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 to care: https://github.com/pgadmin-org/pgadmin4/issues/8712 > (I had to ask somebody 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 > the blinking caret, I have to ask: is there any chance that this will be > cared about within a meaningful timeframe? I'm not exaggerating in the > least when I claim that at least to me, this is a critical bug which > seriously prevents 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 t= o > care about. How are you all able to think and type in the SQL query or do > anything else in the application when there's a blinking caret which > constantly steals your focus and attention? > > > --00000000000061654f063b2289d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Mullvadisen,

We have prioritize= d the issue and added it to the current sprint. It should be resolved in th= e next release (v9.7). We'll assess the feasibility and keep you update= d.

On Tue, Jul 29, 2025 at 7:13=E2=80=AFPM mullv= adisen <mullvadisen@proton.me> wrote:
Th= ree months ago, I sent an e-mail to this list about two serious annoyances = which crippled my use of pgAdmin completely.

One of them was that it had begun showing a white "flash" each ti= me you opened a new "page", before drawing the real (dark) backgr= ound. This was luckily fixed shortly afterwards.

However, the second issue, the hardcoded blinking caret which doesn't r= espect system settings nor has any preference to turn it off inside pgAdmin= , remains. 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 tak= e for anyone to care:
https://github.com/pgadmin-= org/pgadmin4/issues/8712 (I had to ask somebody else to post it on Gith= ub because that site doesn't let me register an account.)

Since Mozilla and others has ignored important issues for decades, and I= 9;m literally screaming from frustration every time I'm using pgAdmin d= ue to the blinking caret, I have to ask: is there any chance that this will= be cared about within a meaningful timeframe? I'm not exaggerating in = the least when I claim that at least to me, this is a critical bug which se= riously prevents me from using the program. It really is that annoying. I a= lways out of necessity turn off blinking cursors and any other animated ele= ments 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 con= stantly steals your focus and attention?


--00000000000061654f063b2289d3--