{"push_id":1152337677,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"409bde0fc32e983a6bf98f35113bc41af30f5d74","before":"d0035d20d7300144e6fe6d049259706f9ebe4d87","commits":[{"sha":"409bde0fc32e983a6bf98f35113bc41af30f5d74","author":{"name":"Charles Marsh","email":"9a65f4850753c7446e0f8a24d00afda8ff2e5285@khanacademy.org"},"message":"Pass keypad node to `onFocusChange` callback\n\nSummary:\n...to allow clients to account for the keypad's presence, when an input is focused.\n\nOn the site, we have plenty of page content below our exercises such that there will always be\nenough space to scroll an input out from under the newly visible mobile web keypad. However, in our\nmobile apps, there's no such accommodation; as such, we need to dynamically add padding to the page\nwhenever an input is focused. In order to compute the appropriate amount of padding, we need to\nprovide the native apps with the relevant DOM node.\n\nOn Asana @ https://app.asana.com/0/132409062806753/142235863904716.\n\nTest Plan: Coming in the native integration diff.\n\nReviewers: benkomalo\n\nReviewed By: benkomalo\n\nSubscribers: jared\n\nDifferential Revision: https://phabricator.khanacademy.org/D28046","distinct":true,"url":"https://api.github.com/repos/Khan/perseus/commits/409bde0fc32e983a6bf98f35113bc41af30f5d74"}]}
{"actor":{"display_login":"crm416"}}