We currently set this flag and then remove it with a timeout of 0 so that only the next focus event in the lifecycle deals with that value of the flag, but I'm wondering if that really makes sense -- I'd like to suggest we clear it in a tolerably low timeout because some things set the focus programmatically and have to yield and this causes it to wind up with the wrong answer. 250 is probably low enough, but even 100 is better than 0 maybe.
We currently set this flag and then remove it with a timeout of 0 so that only the next focus event in the lifecycle deals with that value of the flag, but I'm wondering if that really makes sense -- I'd like to suggest we clear it in a tolerably low timeout because some things set the focus programmatically and have to yield and this causes it to wind up with the wrong answer. 250 is probably low enough, but even 100 is better than 0 maybe.