edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Disabling local echo for password fields
Date: Mon, 10 Jul 2017 21:32:38 -0700	[thread overview]
Message-ID: <87tw2joaop.fsf@the-brannons.com> (raw)
In-Reply-To: <20170710045636.GA3943@nautica> (Dominique Martinet's message of "Mon, 10 Jul 2017 06:56:36 +0200")

Dominique Martinet <asmadeus@codewreck.org> writes:

> Right, I hadn't thought of radio and other type of fields as there
> weren't any on the page I tested.
> I agree something will likely break in that case, but I would like to
> disable echo for informations entered with that even if the field is not
> set -- I think in that case it makes more sense to revert INP_PW as a
> minor type, I will implement that as you suggested in your earlier mail.

The inp_types list in decorate.c is also duplicated in html.c, and you
missed that one in the patch to add the new minor type.
Couldn't we just get rid of the inp_types from html.c and make inp_types
from decorate.c global?
Maybe some of these constant strings belong in their own file, like
html-constants.c or whatever, but that's a discussion for another day.

I'd also say that the function infShow needs to be reworked a little, so
that it shows the minor type, and not just text.
I'd like Karl's opinion on that.  If he agrees, I wouldn't mind doing
that work after your patches are submitted.

Aside from all of that, your patchset looks pretty good.
I still want Adam's opinion on the auth negotiation.  I don't know if
his issue still exists, or whether it was subsequently fixed by libcurl
/ other software.

Regards,
-- Chris

  reply	other threads:[~2017-07-11  4:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  5:19 Dominique Martinet
2017-07-03 11:29 ` Karl Dahlke
2017-07-07 12:13   ` Chris Brannon
2017-07-07 13:35     ` Dominique Martinet
2017-07-09 14:40   ` Dominique Martinet
2017-07-09 15:45     ` Karl Dahlke
2017-07-09 21:45     ` Karl Dahlke
2017-07-10  4:56       ` Dominique Martinet
2017-07-11  4:32         ` Chris Brannon [this message]
2017-07-12  6:11           ` Dominique Martinet
2017-07-12 12:27             ` Chris Brannon
2017-07-12 12:55               ` Dominique Martinet
2017-07-12 14:32                 ` Chris Brannon
2017-07-12 15:02                   ` Dominique Martinet
2017-07-12 22:00                     ` Chris Brannon
2017-07-12 16:56                   ` Karl Dahlke
2017-07-12 12:44             ` Karl Dahlke
2017-07-15 11:29               ` Dominique Martinet
2017-07-15 12:27                 ` Chris Brannon
2017-07-15 23:42                   ` Karl Dahlke
2017-07-16  2:22                 ` Chris Brannon
2017-07-17 14:04                 ` Chris Brannon
2017-07-17 14:39                   ` Dominique Martinet
2017-07-17 14:45                     ` Chris Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tw2joaop.fsf@the-brannons.com \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=asmadeus@codewreck.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).