{"action":"created","issue":{"url":"https://api.github.com/repos/STRML/react-grid-layout/issues/129","labels_url":"https://api.github.com/repos/STRML/react-grid-layout/issues/129/labels{/name}","comments_url":"https://api.github.com/repos/STRML/react-grid-layout/issues/129/comments","events_url":"https://api.github.com/repos/STRML/react-grid-layout/issues/129/events","html_url":"https://github.com/STRML/react-grid-layout/issues/129","id":118490352,"number":129,"title":"Tracking `next` release","user":{"login":"STRML","id":1197375,"avatar_url":"https://avatars.githubusercontent.com/u/1197375?v=3","gravatar_id":"","url":"https://api.github.com/users/STRML","html_url":"https://github.com/STRML","followers_url":"https://api.github.com/users/STRML/followers","following_url":"https://api.github.com/users/STRML/following{/other_user}","gists_url":"https://api.github.com/users/STRML/gists{/gist_id}","starred_url":"https://api.github.com/users/STRML/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/STRML/subscriptions","organizations_url":"https://api.github.com/users/STRML/orgs","repos_url":"https://api.github.com/users/STRML/repos","events_url":"https://api.github.com/users/STRML/events{/privacy}","received_events_url":"https://api.github.com/users/STRML/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-11-23T22:44:26Z","updated_at":"2015-12-24T11:06:28Z","closed_at":null,"body":"As many have you been awaiting, the `next` branch:\r\n\r\n* Contains a refactor of most of the project\r\n* Has React 0.14 Support\r\n* Has better IE/Touch compatibility\r\n* Is fully validated using Flow\r\n* Uses mainline React-Draggable and React-Resizable (1.x versions).\r\n\r\nMuch of the difficulty in this branch involves a rethinking of how we manage state in child components and a move toward a completely stateless `<Draggable>`, which is not yet integrated in RGL.\r\n\r\nThis issue is tracking the release of this branch. See also discussion in #117.\r\n\r\nBlockers:\r\n\r\n- [x] React-Draggable 1.x is calling back with clientX/Y when it should be sending offsetX/Y. This is causing a bad 300px offset in the demo. (fixed in https://github.com/mzabriskie/react-draggable/commit/c1a5bb3daaebfef07512fabf9dfbd435279241c8)\r\n- [ ] Draggable is not following mouse position with placeholder in the grid, it is instead following the placeholder directly. For example:\r\n  -  **(Correct, old branch)** ![screen shot 2015-11-23 at 4 40 34 pm](https://cloud.githubusercontent.com/assets/1197375/11352269/09846b96-9201-11e5-8d77-07fe874ed111.jpg)\r\n  - **(Incorrect, `next` branch)** ![screen shot 2015-11-23 at 4 40 55 pm](https://cloud.githubusercontent.com/assets/1197375/11352271/1489d76a-9201-11e5-9fd1-dd1012f04b8c.jpg) \r\n- [ ] Use `<DraggableCore>` directly and store state in RGL, rather than in each `<Draggable>`.\r\n\r\nStretch goals:\r\n\r\n- [ ] Once onto `<DraggableCore>`, we can use percentage top/left and height/width directly. This will not only allow us to stop listening for resize events, but do more proper server-side rendering.\r\n  - Can we still use CSS transforms with percentages? CSS transform percentages are relative to the element's width/height, not the offsetParent's width/height. We could trick it by measuring the offsetParent and doing the math with JS, but we lose the server-rendering benefits as above.\r\n"},"comment":{"url":"https://api.github.com/repos/STRML/react-grid-layout/issues/comments/167093908","html_url":"https://github.com/STRML/react-grid-layout/issues/129#issuecomment-167093908","issue_url":"https://api.github.com/repos/STRML/react-grid-layout/issues/129","id":167093908,"user":{"login":"Puffton","id":12534742,"avatar_url":"https://avatars.githubusercontent.com/u/12534742?v=3","gravatar_id":"","url":"https://api.github.com/users/Puffton","html_url":"https://github.com/Puffton","followers_url":"https://api.github.com/users/Puffton/followers","following_url":"https://api.github.com/users/Puffton/following{/other_user}","gists_url":"https://api.github.com/users/Puffton/gists{/gist_id}","starred_url":"https://api.github.com/users/Puffton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Puffton/subscriptions","organizations_url":"https://api.github.com/users/Puffton/orgs","repos_url":"https://api.github.com/users/Puffton/repos","events_url":"https://api.github.com/users/Puffton/events{/privacy}","received_events_url":"https://api.github.com/users/Puffton/received_events","type":"User","site_admin":false},"created_at":"2015-12-24T11:06:28Z","updated_at":"2015-12-24T11:06:28Z","body":"Why are the children id's forced to be ints now? It's a breaking change for me, so I was just wondering if there was a good reason."}}