On Mar 5, 2014, at 3:05 PM, Luther Baker <lutherba...@gmail.com> wrote:
>> The only way to find out is to file a radar and see what comes out in iOS > 8. > > 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 > .... to ask that secure text fields not echo their contents in Plaintext. Filing a bug *is* how you influence Apple. Or, buy a few million shares. Or become a head of engineering. I mean seriously, if everyone had the same amount of influence, then iOS would be Android. > I guess its no big deal when you think of the naive device use case - where > someone could simply watch your fingers type on the virtual keyboard ... > but demos are often on mirrored devices or sometimes use hardware keyboards > or are fired up the simulator and displayed on the big screen as the team > watches in earnest to see the week's progress. Perhaps a good bug report is that the user’s screen works the same way it does now, but if its mirrored - then the mirrored screen keeps he password hidden. That would be a good use case. > > Again, I'm OK with it. I like writing custom controls. Just find it > interesting ... there has to be _some_ reason we haven't uncovered yet :) > Wanted to see if anyone had an elegant solution or if I'd missed something > in the API. The good reason was already provided - MOST people cannot enter a password on a soft keyboard without seeing the character they just pressed. _______________________________________________ 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
