Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMkxC-0000lh-Jq for pgadmin-support@arkaria.postgresql.org; Fri, 10 Apr 2020 04:07:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jMkxA-0003To-8H for pgadmin-support@arkaria.postgresql.org; Fri, 10 Apr 2020 04:07:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMkx9-0003TZ-Sw for pgadmin-support@lists.postgresql.org; Fri, 10 Apr 2020 04:07:40 +0000 Received: from mail-lj1-x241.google.com ([2a00:1450:4864:20::241]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jMkx2-0000t9-G1 for pgadmin-support@postgresql.org; Fri, 10 Apr 2020 04:07:38 +0000 Received: by mail-lj1-x241.google.com with SMTP id n17so739460lji.8 for ; Thu, 09 Apr 2020 21:07:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OUAPzxLYbajB4LDbPxQg+g28C6ZGYF4C7dNAUJJzb7E=; b=PFLnnQvrCvkYzABpDCFj0htA4aOaD5rqHLCjdIbRwqfRkC2JQk2fX5k1xwDtuhlsPS P5or6X9X1X1rSpxijg3LLlXuF95nDZQBKrBs9ManBs7PWT16qHs3/LMgUJzTBxO5czdp KTfaI8zvGKDrYsyfLQj81wpuNl1i8HFh7vukOsY7Ra36mzwcZdoiy1+g7k3DaGkNrLWt VlT9/A9Sup5kimZNZaY0aAHRywvEUFr3DeFaboNWdLHH1w8H7yNSjk4NFEIpzAgstM8t DFFHSG5KtaK4qzqA8J7fqmPJ6qLFLpUqP3h9FNNfMIT1Tezcsir7BPmVg2/7h05RpmNg b5DA== 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=OUAPzxLYbajB4LDbPxQg+g28C6ZGYF4C7dNAUJJzb7E=; b=GXRyOuWYZ3Z2byZCkdVv3k1DHRoLtr5R09nCDztCxMUThD0T0NF7GfeSNotShYS6m/ f6xaghPL3x2ZaPJYY/l5u5sZDmNPmklbCREeyTUe7MmNpxVtZtq0V9nA28oSZXFhv4el QFD+IOrYmEYFPR1vTVwbIZxGSy5Y2Ma2irDcHZFNJpybJ9URL8GsjkaDvVZf41IEpBF8 LiRnB2XjNE8LLa4e6z1fGtcalKBYzQTWDWCNsRJSoT/zQGUW+GAQouRSeYYsBsgO+fyb 1/LqWNNPhmdSEs4O+FBusDH5hlzSVlqmy/+zpyGzRttChc0HbV9lhGTfcxSGv0R3n6wR fd/w== X-Gm-Message-State: AGi0PuZpTKWmZlXtdR8NYrzZ+y1zfhw1N1GalI1QVGM2BSpks4AJd8Zj HrKL8Y0zrGqc3iaaKq+4T/vP4f8cfHgpl9XWmpk4Kx990vZ1xN4WHEBp9lwiAES/xMWDHxD01Hb kGHFV2t6U0v705tIS0TUXJRiW3+Fq/BujAqd9xEBK/pexvBQRjERJVeqAbAXWxiSlvQbxA1SRj6 qlzA3XVoa9j+68G/KLLNq926i17r1nraD+mqvmupzbI/sc2dM2S1k= X-Google-Smtp-Source: APiQypINckWI3FziR5Plps21tBtInSofDbQzDDIo8YUnLmh6FHK+jAIk5ECByZd95LeH4HMrk8S5JL4t7muxCNc5ui8= X-Received: by 2002:a2e:90ce:: with SMTP id o14mr744664ljg.92.1586491650526; Thu, 09 Apr 2020 21:07:30 -0700 (PDT) MIME-Version: 1.0 References: <1e6b5a0b-2fc9-1cac-f13a-bcc84f02e00e@darrenduncan.net> <6148f1ed-8eee-931e-06a1-23c64d790cf5@darrenduncan.net> In-Reply-To: <6148f1ed-8eee-931e-06a1-23c64d790cf5@darrenduncan.net> From: Khushboo Vashi Date: Fri, 10 Apr 2020 09:37:23 +0530 Message-ID: Subject: Re: Proposal: Drop support for Internet Explorer To: Darren Duncan Cc: Dave Page , pgAdmin Support , pgadmin-hackers , Akshay Joshi Content-Type: multipart/alternative; boundary="00000000000044f03b05a2e7dfd7" X-CLOUD-SEC-AV-Info: edb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000044f03b05a2e7dfd7 Content-Type: text/plain; charset="UTF-8" On Thu, Apr 9, 2020 at 11:57 PM Darren Duncan wrote: > The patch looks good as much as I understand it, but this raises an > important > question: > > How should one best handle minority browsers that may be completely modern > but > you may not specifically know about them? Such as the newer crop of > browsers > that emphasize stronger privacy or may have fewer identifiers? > > While going on a whitelist as the patch essentially does for known good > browsers > is conservative, I feel that an alteration would be good. > > I propose dividing the browsers/environments into 3 categories, which are > recognized-supported, recognized-unsupported, and unrecognized. > > So the unsupported older versions of supported browsers get a stronger > message > encouraging a browser switch as they are recognized as unsupported, while > unrecognized browsers get a different weaker message saying they weren't > recognized so we can't determine if they'd work; both can point to the > list of > known supported browsers. > > I do agree with this suggestion. > Related to this, there could be an application toggle that affects the > unrecognized category where users can basically say, yes I understand you > don't > recognize this browser, please hide the warning, or something like that. > > Also, it probably goes without saying, but the code/templates will need to > be > structured in such a way that the warning message uses about plain as > possible > HTML so that if the browser doesn't support displaying the UI in general > it can > at least display the message. > > -- Darren Duncan > > On 2020-04-09 4:36 a.m., Dave Page wrote: > > Hi > > > > On Thu, Apr 9, 2020 at 12:26 AM Darren Duncan wrote: > > > > If its hard to know how many people are actually using Internet > Explorer: > > > > You could make the next release of pgAdmin display a message > occasionally to > > users of Internet Explorer saying that Internet Explorer will no > longer be > > officially supported in a future version, and when that version > comes the > > message says now no longer supported. > > > > You can then see how many people contact you about this to express > concern. > > > > > > Good idea. I've hacked up a patch to warn users if they're using a > deprecated or > > unsupported browser. > > > > CCing Akshay for a review :-) > > > > -- > > Dave Page > > Blog: http://pgsnake.blogspot.com > > Twitter: @pgsnake > > > > EnterpriseDB UK: http://www.enterprisedb.com > > The Enterprise PostgreSQL Company > > > > --00000000000044f03b05a2e7dfd7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Apr 9, 2020 at 11:57 PM Darre= n Duncan <darren@darrenduncan= .net> wrote:
The patch looks good as much as I understand it, but this raises an imp= ortant
question:

How should one best handle minority browsers that may be completely modern = but
you may not specifically know about them?=C2=A0 Such as the newer crop of b= rowsers
that emphasize stronger privacy or may have fewer identifiers?

While going on a whitelist as the patch essentially does for known good bro= wsers
is conservative, I feel that an alteration would be good.

I propose dividing the browsers/environments into 3 categories, which are <= br> recognized-supported, recognized-unsupported, and unrecognized.

So the unsupported older versions of supported browsers get a stronger mess= age
encouraging a browser switch as they are recognized as unsupported, while <= br> unrecognized browsers get a different weaker message saying they weren'= t
recognized so we can't determine if they'd work; both can point to = the list of
known supported browsers.

I do agree with this suggestion.
=C2=A0
Related to this, there could be an application toggle that affects the
unrecognized category where users can basically say, yes I understand you d= on't
recognize this browser, please hide the warning, or something like that.
Also, it probably goes without saying, but the code/templates will need to = be
structured in such a way that the warning message uses about plain as possi= ble
HTML so that if the browser doesn't support displaying the UI in genera= l it can
at least display the message.

-- Darren Duncan

On 2020-04-09 4:36 a.m., Dave Page wrote:
> Hi
>
> On Thu, Apr 9, 2020 at 12:26 AM Darren Duncan wrote:
>
>=C2=A0 =C2=A0 =C2=A0If its hard to know how many people are actually us= ing Internet Explorer:
>
>=C2=A0 =C2=A0 =C2=A0You could make the next release of pgAdmin display = a message occasionally to
>=C2=A0 =C2=A0 =C2=A0users of Internet Explorer saying that Internet Exp= lorer will no longer be
>=C2=A0 =C2=A0 =C2=A0officially supported in a future version, and when = that version comes the
>=C2=A0 =C2=A0 =C2=A0message says now no longer supported.
>
>=C2=A0 =C2=A0 =C2=A0You can then see how many people contact you about = this to express concern.
>
>
> Good idea. I've hacked up a patch to warn users if they're usi= ng a deprecated or
> unsupported browser.
>
> CCing Akshay for a review :-)
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company



--00000000000044f03b05a2e7dfd7--