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: Wed, 12 Jul 2017 05:27:18 -0700	[thread overview]
Message-ID: <874luhon6h.fsf@the-brannons.com> (raw)
In-Reply-To: <20170712061115.GA3270@nautica> (Dominique Martinet's message of "Wed, 12 Jul 2017 08:11:15 +0200")

Dominique Martinet <asmadeus@codewreck.org> writes:

> I have done just that: removed inp_types in html.c and declared as
> extern in eb.h
> I think 'number' might also need to be moved to minor, but did not take
> the time to change that.

I think the itype_minor idea is a good one, because all these minor
types are just text for the purposes of edbrowse.  We can add new
ones if we ever need to do that; they'll still be handled as text.
The thing I'm a little concerned about is the loss of information.
I didn't really think this through when I read your patches yesterday.
When ipass is used successfully to edit a form field, its itype_minor
automatically becomes INP_PW.  That loses the old itype_minor.  There
may be cases where we need it, E.G., for the DOM.
For instance, what if some JS code needs to find the fields having type
"email"?  This is a bit contrived.
Perhaps we should add a "maskedText" flag to struct htmlTag, set that in
ipass, and use it to determine whether or not to print the stars for
masked fields?  Or maybe my concern is overblown, I don't know.

Sorry for being a harsh reviewer.  I really do like your work,
and I want to see it merged.

-- Chris

  reply	other threads:[~2017-07-12 12:26 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
2017-07-12  6:11           ` Dominique Martinet
2017-07-12 12:27             ` Chris Brannon [this message]
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=874luhon6h.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).