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
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
