Steps: 1. Launch the marketplace app 2. Select the email text field 3. Start typing your email Expected: As I type something from the keyboard, the text typed should appear relatively quickly (high response time). Actual: The delay time for the text to appear is definitely evident. It takes a few seconds for text to appear sometimes in the email field of the persona pop-up.
Text input seems to work as expected for me. I'm on a 2012-08-29 nightly. Can you reliably reproduce?
Just reflashed my device to a clean 8/29 build and started from the STR right from the beginning. I can definitely reproduce this reliably.
I can't open the Marketplace app on my device with a clean 8/30 build :) I can see JST trying the "Dev Marketplace" app and the first few characters typed into the email field are definitely delayed but after 3 or so it seems to be alright. If the main Marketplace app does this, too, then this should block. With paint flashing on it's clear that a lot of the login panel is being repainted all the time.
Ben, if you're not the right person to investigate here, please re-assign. Thanks.
Ben, are you the right owner here? If so, any updates and/or eta here?
I will investigate. Anecdotally, I have noticed that text input in the native popup or trusted UI is much more responsive than the persona shim in a separate tab. Hoping that there's not much more to do here than get the native implementation done :)
Lawrence and I were looking at this just now. His experience is that this is general text input performance and not Persona-specific. That being said, there was no lag when he tried it just now on his Unagi with the Dev Marketplace. Jason, can you still reproduce? What about text input outside of the Marketplace login?
we've noticed this unagi/otoro difference, too, and have been wondering if we need to target otoro performance. We're not doing anything all that special on that login screen when email address is entered, just a tiny bit of computation.
John H. and myself re-tested and can't reproduce. Don't know what fixed this bug.
I'm experiencing this since a couple of weeks on Nexus S. Anyone able to reproduce with recent builds on supported devices ?