edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Disabling local echo for password fields
Date: Wed, 12 Jul 2017 08:44:00 -0400	[thread overview]
Message-ID: <20170612084400.eklhad@comcast.net> (raw)
In-Reply-To: <20170712061115.GA3270@nautica>

Yes, number is another minor type of text.
If you're making password a minor text type then number should be as well, if you don't mind and if you have the time.
Later on we can use this minor type to constrain the input, as other browsers do.
number has an obvious syntax, so does email, etc.

sure, infshow() should print text(number) or some such.

I continue my concern about overwriting or changing what html has declared, and Chris shares this concern.
This is just philosophy for now, can't think of a real-world issue, it just makes me queasy.
The mask bit would get around this.

bool masked:1;

Put this in with all the other boolean members in struct htmlTag.
Every struct I allocate is set to zero so you don't have to worry about that.
Add a new member and it is automatically false from the start.
The ipass command could set it to true, and then you could test

if(t->masked || t->inp_minor == INP_PW) { put in stars }

> We cannot change the command name once this is merged so now is a good

Right.
ipass or ipass2 or ipass$ it's not my favorite convention but truly I can't think of anything better.
It's so rarely used, and I'd never use it at all (personally), so in that sense I don't care.
Well I think it's fine if others agree.

Karl Dahlke

  parent reply	other threads:[~2017-07-12 12:43 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
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 [this message]
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=20170612084400.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).