{"push_id":1091686603,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"9d3da64afb2a514fc4d3117e47b05e4f87df1d25","before":"3001e47907ce5ac28a0d5a25b0e144c48127d09a","commits":[{"sha":"9d3da64afb2a514fc4d3117e47b05e4f87df1d25","author":{"email":"6229a3e4f86172a005a6eaab5029d1bd13acce1f@fb.com","name":"Isaac Salier-Hellendag"},"message":"Fix deletion behavior around atomic blocks\n\nSummary:\nThere is currently a selection state bug for deletion behavior around atomic blocks. Namely, removing an atomic block from a neighboring block will remove the atomic block but leave the cursor in an invalid state.\n\nMake it so that atomic blocks will be removed during:\n\n- Forward deletion from the last offset of a preceding block\n- Backward deletion from the zero offset of a following block\n\ntasti and I discussed whether there should be some special behavior for forward deletion from an empty preceding block, i.e. removing the current block and moving the cursor upward, but this seemed magical.\n\nWe can try this out and adjust the behavior as needed.\nCloses https://github.com/facebook/draft-js/pull/332\n\nReviewed By: ezequiel\n\nDifferential Revision: D3245579\n\nfb-gh-sync-id: a250cf87515f225d13e1da30023b9fb681e06ef5\nfbshipit-source-id: a250cf87515f225d13e1da30023b9fb681e06ef5","distinct":true,"url":"https://api.github.com/repos/facebook/draft-js/commits/9d3da64afb2a514fc4d3117e47b05e4f87df1d25"}]}