{"push_id":1200493461,"size":1,"distinct_size":1,"ref":"refs/heads/use-selection-polling","head":"2ff05908fbe03ff48f3da16523825bb2c73383aa","before":"99578923f68e8b5353edb197c1ed6905f2de5268","commits":[{"sha":"2ff05908fbe03ff48f3da16523825bb2c73383aa","author":{"name":"Cory Forsyth","email":"e88e4c6cf541f4c619759468a5a4b17141c731fb@gmail.com"},"message":"Add SelectionChangeObserver, use it for editor.range updates\n\nSelectionChangeObserver maintains a singleton instance that polls the\nwindow using `requestAnimationFrame` for changes to the selection.\nEditors' EventManager instances use a SelectionManager to listen for\n`selectionchanged` events, and update the editor's `range` if necessary.\n\nRemoves code that would use some keyup events (when `key.isMovement()`)\nand `mouseup` events to detect when the range could have changed.\n\nThe range-detection code was previously spread out over `EventManager`,\n`Editor`, `Cursor` and `EditState`. This code change consolidates most\nof the responsibility for knowing/reading/updating the editor's `range`\no its `EditState` instance. The editor now delegates `range` to the edit\nstate instance, and the edit state instance is responsible for knowing\nwhen the editor's inputMode or range has changed.\n\nSome tests assumed selection changes would be picked up synchronously;\nfor those tests a `Helpers.wait` helper is added that schedules a\ncallback with `requestAnimationFrame`.\n\nAlso:\n * use \"hidepassed\" for sauce tests to improve test failure debugging\n * remove unused `editor.selectSections`\n * remove now-unnecessary key commands for meta+arrow on mac","distinct":true,"url":"https://api.github.com/repos/bustlelabs/mobiledoc-kit/commits/2ff05908fbe03ff48f3da16523825bb2c73383aa"}]}
{"actor":{"display_login":"bantic"}}