payload: {"push_id":4076731759,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"efb7bf434f2c993dc0f44a83fa13efcda127526a","before":"0bfca375b3f5732a5b14a3b56653ab1a35442e94","commits":[{"sha":"efb7bf434f2c993dc0f44a83fa13efcda127526a","author":{"name":"Michael Klimushyn","email":"c39f2d977676b82993656ba1f457c9c53bfbe72f@google.com"},"message":"Work around Samsung keyboard issue (#12432)\n\nSamsung's Korean keyboard has a bug where it always attempts to combine\r\ncharacters based on its internal state, ignoring if and when the cursor\r\nis moved programmatically. EG typing \"ㄴㅇ\" and then moving the cursor\r\nback to the front of the text and typing \"ㄴ\" again would result in\r\n\"ㄴㅇㄴ\", not \"ㄴㄴㅇ\".\r\n\r\nFully restarting the IMM works around this because it flushes the\r\nkeyboard's internal state and stops it from trying to incorrectly\r\ncombine characters. However this also has some negative performance\r\nimplications, so we only apply the workaround on Samsung devices set\r\nto use Korean input.\r\n\r\nThis also effectively disables the feature on Samsung keyboards that\r\nallowed users to re-open a composing region for previously typed\r\ncharacters. See https://github.com/flutter/flutter/issues/29341#issuecomment-531283508.\r\n\r\nFixes flutter/flutter#29341.","distinct":true,"url":"https://api.github.com/repos/canewsin/engine/commits/efb7bf434f2c993dc0f44a83fa13efcda127526a"}]}
other: {"actor":{"display_login":"pull"}}