Bugzilla – Bug 13047
email entry allows invalid characters, upper case (or add repeated version of
Last modified: 2011-11-06 23:24:27 UTC
Email entry should only allow valid email characters -- greatly reduces the amount of scrolling needed to enter an email (very important during setup). Also, is upper & lower case necessary? Seems like an email entry form should only list lowercase letters.
Aren't some mail servers case sensitive?
"Hardly any email service or ISP does enforce case sensitive email addresses, returning messages whose recipient's email address was not typed correctly (in all upper case, for example)." ~ http://email.about.com/od/emailbehindthescenes/f/email_case_sens.htm Hm, I wish there was a way to quantify that. If it's .01% of mail servers, then it's best to forget about case in email entry. Wonder if we can get data on this.
I'm mostly joking when I say this but... ...if any email servers do this wrong, it wouldn't surprise me if Lotus Notes is one of them.
Haha, no fortunately Lotus Notes mail servers are not case sensitive. At least, not Logitech's.
Targeting for next release
What's there is already the list of valid email characters. Moving to P2 for the remaining issue: There has been talk of repeating @ and . (I can't find the bug for this). Here are campfire notes on that. Tom W. Does anyone know if there is a bug for the talked of idea of having , for instance, more than one "@" character in the list of scrolling letters when you are entering an email address on baby/jive? I can't find one. There's 13047. but that's different (and not valid, since we already show only the valid characters). Also, if there isn't a bug, does this seem like a P1 issue. I looked into it briefly, and it is a bit of a challenge to code (3-4 hours I would guess), since our code doesn't support repeated chars in the input chars list well... 2:30 PM Tom W. Just taking a stab at it I was thinking instead of: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!#$%&'*+-/=?^_`{|}~0123456789@. fo oop, do abcdefghijklmnopqrstuvwxyz@.ABCDEFGHIJKLMNOPQRSTUVWXYZ@.+-_!#$%&'*/=?^`{|}~0123456789@. given that @ and . are the most commonly needed things in an email, plus I move + - and _ next to the @. since I think those are the next most common. Mickey G. P1? you sure? Tom W. I'm asking, should it be P1 2:35 PM Pat R. Tom - Its a P2. There are lots of things like this that I'd like to fix but if we do, we won't ship on time. Tom W. will do, updating the 13047 bug, which I am making the char list improvement bug....
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Moving these bugs to P4 to make room for moving P1.5 bugs to P2
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Moving lower-priority bugs to next target
Tom is no longer available to us
Unassigned bugs cannot have a priority.