On Mar 5, 2014, at 14:05 , Luther Baker <lutherba...@gmail.com> wrote:
> But I don't think this really justifies the decision. My daughter > dropped the iPad on her toe but I don't think that warrants rubber bumpers > on the device :) Just to emphasize: I wasn’t making a witticism. It’s a genuine problem — especially given that in some cases entering multiple incorrect attempts will get you locked out of an account. Showing the password in plain text while it’s being typed *isn’t* a flaw from my point of view. Incidentally, having a “fully obscured” custom text field won’t help you in the demo scenario, because the audience can still see the key images pop up on the keyboard as you type. Are you proposing removing that feedback too? (And how will you do that?) > How very sad ... there should really be no way I could influence Apple in > this regard. IE: this isn't some elaborate, hard to define bug. This better > not be an accident that requires energy from someone as insignificant as me I agree with the earlier post which said (more or less) that if it’s your job to demo stuff, then it’s also your (your company’s) responsibility to provide a non-secure demo platform, or a non-secure account. Your position is a bit inconsistent here. You can’t express disappointment in Apple’s lack of assiduity, and simultaneously say it’s too much trouble for you to take elementary steps to avoid exposing your keystrokes (e.g. pasting in the password, or disconnecting your device from the public display while you log in, or providing test credentials, etc). _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
