{"action":"opened","issue":{"url":"https://api.github.com/repos/kangax/fabric.js/issues/2361","labels_url":"https://api.github.com/repos/kangax/fabric.js/issues/2361/labels{/name}","comments_url":"https://api.github.com/repos/kangax/fabric.js/issues/2361/comments","events_url":"https://api.github.com/repos/kangax/fabric.js/issues/2361/events","html_url":"https://github.com/kangax/fabric.js/issues/2361","id":97381635,"number":2361,"title":"Bounding box position breaks on canvas mouse up","user":{"login":"sibbaldl","id":505678,"avatar_url":"https://avatars.githubusercontent.com/u/505678?v=3","gravatar_id":"","url":"https://api.github.com/users/sibbaldl","html_url":"https://github.com/sibbaldl","followers_url":"https://api.github.com/users/sibbaldl/followers","following_url":"https://api.github.com/users/sibbaldl/following{/other_user}","gists_url":"https://api.github.com/users/sibbaldl/gists{/gist_id}","starred_url":"https://api.github.com/users/sibbaldl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sibbaldl/subscriptions","organizations_url":"https://api.github.com/users/sibbaldl/orgs","repos_url":"https://api.github.com/users/sibbaldl/repos","events_url":"https://api.github.com/users/sibbaldl/events{/privacy}","received_events_url":"https://api.github.com/users/sibbaldl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-07-27T04:02:01Z","updated_at":"2015-07-27T04:02:01Z","closed_at":null,"body":"Hi everyone\r\n\r\nCross posting this here from google groups for extra coverage:\r\n\r\nhttps://jsfiddle.net/sibbaldl/uutL3oje/\r\n\r\nThere's some instructions in the Fiddle JS but in a nutshell, if we draw a doodle on to a canvas, group the individual paths, and then set active the group, everything seems fine. We can move the paths around as a single group. However, if we then click away from the object so that it is deselected, the bounding box position remains in the correct location but the actual path group itself jumps to a bottom right offset. \r\nI've tried adjusting the grouping code to see if I could affect the outcome but nothing really makes much difference - I thought setCoords() might be responsible but removing it doesn't help.\r\n\r\nNote that in 1.6RC1 the paths actually disappear rather than be shown at an offset (unless the offset is absolutely miles away and I just can't see it).\r\n\r\nAny help gratefully received\r\n\r\nCheers\r\n\r\nLee"}}