Skip to content
This repository has been archived by the owner on Jun 25, 2019. It is now read-only.

timing issue #21

Open
bkardell opened this issue Jul 29, 2015 · 0 comments
Open

timing issue #21

bkardell opened this issue Jul 29, 2015 · 0 comments

Comments

@bkardell
Copy link
Contributor

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.

bkardell added a commit to bkardell/modality that referenced this issue Aug 4, 2015
bkardell added a commit that referenced this issue Aug 4, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant