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 1jONnK-000621-DD for pgadmin-support@arkaria.postgresql.org; Tue, 14 Apr 2020 15:48:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jONnI-0001h4-QL for pgadmin-support@arkaria.postgresql.org; Tue, 14 Apr 2020 15:48:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jONnI-0001gv-FQ for pgadmin-support@lists.postgresql.org; Tue, 14 Apr 2020 15:48:12 +0000 Received: from mail-il1-x143.google.com ([2607:f8b0:4864:20::143]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jONnF-0006ze-3n for pgadmin-support@postgresql.org; Tue, 14 Apr 2020 15:48:11 +0000 Received: by mail-il1-x143.google.com with SMTP id d2so198942ilc.0 for ; Tue, 14 Apr 2020 08:48:08 -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=ZsMhV5a89LmJ62oxwiiz4NF68AOH1kRJV5h+XqHvKwI=; b=vvXOmgshD03MPoqaoaowP+K8GR9npUf5hWayr/G42iISBK/fwDMWBHuCCZ6zxXdeOL 7KYpyfKD67y77d+vYIQtzVZKLFwUMrkAsNDxvkM69MLcdApzMjmdbI1qdLJ14HgMk8UZ /n7uneOpPU0VHRSXBOmgXkqSdU9nv3iOaU2jPTmHtjarR89wncbXbwaIpq5q0v7tZTEA clSWVpEc7to5N6+TARr/JTL+GgbX0oZGExpNsyB8yJq7HKNPUZ/ulpukWt7KPkY2+hz2 b5wZSwG3VD33SXf+wPlq9xm0kPLD0hz009AgWpGIP9hvMbcVboMCuUfAHEWL7GdlVweJ UT3A== 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=ZsMhV5a89LmJ62oxwiiz4NF68AOH1kRJV5h+XqHvKwI=; b=UFalrWfG6Sqq+6KBVJx1gAqbMsm4249MoXRCBjfTdmakB8vsWfEGxywRBmoBJWeJXg 84qqF6wRmX5VGqzaFUF2fdiOq/C5VdeiONhzdx+/7YszyofsaKPsRzkuQrffmGRQJac2 GCvHM+br9ATXH4knBY0Rlx7hsQA6EI7CvItjiXaqNoh1s+CzU3k+a82/s2SDR1RiQ8f8 EkLH6K5uQh7aAT7tFOyKBmV9+7ppmH/astpizgUK2xoN7yljWHSNpw1VEBGZ8VQkylzA CGdofIUNADh0os/ry3XdciyVie9rF8MXxxeowUL4flJs4iYfLra+GsEV/9n0Ft6rX712 9ASg== X-Gm-Message-State: AGi0PuYZ6BnK0dh8aDI9LAqN1OjItrAmvXg1WODt6aNOYO3f5AmtJx2c vVnm+/8vEXBZK/W70a+ZgJZZxS/1KQXQ9rjfehdZ9JHQQGEl3dGHJslXg1bJW4yh3oe5Yed+i4J RmLcFDeDPv334zR7F6WzP2wU0qYy9VQc4KXEb6Tu/Ke6ulHbW/6kVTT6zCvBtCNnuY7cnA6Jv8+ 0+hMTBRHwm6WXdYMVGt9jul2gFRaYiak0QF+QXbgsCIJX5phs6ROQ= X-Google-Smtp-Source: APiQypJImuklGI1vlUJ9woAesD45W99YMjUWuTiC6lr7y7/cNR54M9Hkl13wsnCnHYX/yDNfRMYS1WBrOxF3b75C80w= X-Received: by 2002:a05:6e02:5cb:: with SMTP id l11mr918900ils.236.1586879287275; Tue, 14 Apr 2020 08:48:07 -0700 (PDT) MIME-Version: 1.0 References: <1e6b5a0b-2fc9-1cac-f13a-bcc84f02e00e@darrenduncan.net> <6148f1ed-8eee-931e-06a1-23c64d790cf5@darrenduncan.net> In-Reply-To: From: Akshay Joshi Date: Tue, 14 Apr 2020 21:17:55 +0530 Message-ID: Subject: Re: Proposal: Drop support for Internet Explorer To: Dave Page Cc: Neel Patel , Khushboo Vashi , Darren Duncan , pgAdmin Support , pgadmin-hackers Content-Type: multipart/alternative; boundary="00000000000038636305a34220ac" 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 --00000000000038636305a34220ac Content-Type: text/plain; charset="UTF-8" Thanks, patch applied. On Tue, Apr 14, 2020 at 8:17 PM Dave Page wrote: > Ooops. Thanks for catching that. Here it is. > > On Tue, Apr 14, 2020 at 3:45 PM Neel Patel > wrote: > >> Hi Dave, >> >> Looks like patch is missing in attachment. >> >> Thanks, >> Neel Patel >> >> >> On Tue 14 Apr, 2020, 6:53 PM Dave Page, wrote: >> >>> Here's an updated patch that gives a slightly different message if the >>> browser is unknown vs. unsupported/deprecated. As with the previous patch, >>> the check can be disabled in the config. >>> >>> On Fri, Apr 10, 2020 at 5:07 AM Khushboo Vashi < >>> khushboo.vashi@enterprisedb.com> wrote: >>> >>>> >>>> >>>> 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 >>>>> >>>>> >>>>> >>>>> >>> >>> -- >>> Dave Page >>> Blog: http://pgsnake.blogspot.com >>> Twitter: @pgsnake >>> >>> EnterpriseDB UK: http://www.enterprisedb.com >>> The Enterprise PostgreSQL Company >>> >> > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- *Thanks & Regards* *Akshay Joshi* *Sr. Software Architect* *EnterpriseDB Software India Private Limited* *Mobile: +91 976-788-8246* --00000000000038636305a34220ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, patch applied.

On Tue, Apr 14, 2020 at 8:17 PM Dave= Page <dpage@pgadmin.org> wr= ote:
Ooops. Thanks for catching that. Here it is.

On Tue, Apr 14, 2020 at 3= :45 PM Neel Patel <neel.patel@enterprisedb.com> wrote:
Hi Dave,=C2= =A0=C2=A0

Looks like patch is = missing in attachment.

T= hanks,
Neel Patel


On Tue 14 Apr, 2020, 6:53 PM Dave Page, <dpage@pgadmin.org> w= rote:
Here's an updated patch that gives a slightly different m= essage if the browser is unknown vs. unsupported/deprecated. As with the pr= evious patch, the check can be disabled in the config.

On Fri, Apr 10, 2020= at 5:07 AM Khushboo Vashi <khushboo.vashi@enterprisedb.com= > wrote:
=


=
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 important
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





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake<= br>
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise= PostgreSQL Company


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB= UK: http://www.e= nterprisedb.com
The Enterprise PostgreSQL Company


--
Thanks & Regards
=
Akshay Joshi
Sr. Software Architect
EnterpriseDB Software India Private Limited
=
Mobile: += 91 976-788-8246
--00000000000038636305a34220ac--