{"action":"created","issue":{"url":"https://api.github.com/repos/ibm-js/delite/issues/374","labels_url":"https://api.github.com/repos/ibm-js/delite/issues/374/labels{/name}","comments_url":"https://api.github.com/repos/ibm-js/delite/issues/374/comments","events_url":"https://api.github.com/repos/ibm-js/delite/issues/374/events","html_url":"https://github.com/ibm-js/delite/issues/374","id":55894835,"number":374,"title":"delite/KeyNav: listen click instead pointerdown and avoid double navigation","user":{"login":"AdrianVasiliu","id":1583981,"avatar_url":"https://avatars.githubusercontent.com/u/1583981?v=3","gravatar_id":"","url":"https://api.github.com/users/AdrianVasiliu","html_url":"https://github.com/AdrianVasiliu","followers_url":"https://api.github.com/users/AdrianVasiliu/followers","following_url":"https://api.github.com/users/AdrianVasiliu/following{/other_user}","gists_url":"https://api.github.com/users/AdrianVasiliu/gists{/gist_id}","starred_url":"https://api.github.com/users/AdrianVasiliu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AdrianVasiliu/subscriptions","organizations_url":"https://api.github.com/users/AdrianVasiliu/orgs","repos_url":"https://api.github.com/users/AdrianVasiliu/repos","events_url":"https://api.github.com/users/AdrianVasiliu/events{/privacy}","received_events_url":"https://api.github.com/users/AdrianVasiliu/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-01-29T12:49:17Z","updated_at":"2015-01-29T15:37:13Z","closed_at":null,"body":"Since 7d19b8992684e0d8acf54fbcd93af572ca8fc895, KeyNav triggers navigation on \"pointerdown\" and, if focusDescendants=true, also on \"focusin\". Two questions/issues:\r\n\r\n* Shouldn't it listen to \"click\" rather than \"pointerdown\"?\r\n* Is it intentional that both handlers are called when focusDescendants=true, leading to two calls of `_descendantNavigateHandler()` when clicking a navigateable item?\r\n\r\nHow to reproduce:\r\nLoad https://github.com/ibm-js/delite/blob/master/tests/functional/KeyNavTests.html and click for instance the first \"Apple\" element in the page while monitoring the calls of the \"pointerdown\" and \"focusin\" handlers of KeyNav (say, using console.log or breakpoints).\r\n=> The navigation occurrs on mouse down, while it might be better that it occurs on mouse up.\r\n=> Both handlers are called, and both handlers call the `_descendantNavigateHandler()` method.\r\n"},"comment":{"url":"https://api.github.com/repos/ibm-js/delite/issues/comments/72045073","html_url":"https://github.com/ibm-js/delite/issues/374#issuecomment-72045073","issue_url":"https://api.github.com/repos/ibm-js/delite/issues/374","id":72045073,"user":{"login":"AdrianVasiliu","id":1583981,"avatar_url":"https://avatars.githubusercontent.com/u/1583981?v=3","gravatar_id":"","url":"https://api.github.com/users/AdrianVasiliu","html_url":"https://github.com/AdrianVasiliu","followers_url":"https://api.github.com/users/AdrianVasiliu/followers","following_url":"https://api.github.com/users/AdrianVasiliu/following{/other_user}","gists_url":"https://api.github.com/users/AdrianVasiliu/gists{/gist_id}","starred_url":"https://api.github.com/users/AdrianVasiliu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AdrianVasiliu/subscriptions","organizations_url":"https://api.github.com/users/AdrianVasiliu/orgs","repos_url":"https://api.github.com/users/AdrianVasiliu/repos","events_url":"https://api.github.com/users/AdrianVasiliu/events{/privacy}","received_events_url":"https://api.github.com/users/AdrianVasiliu/received_events","type":"User","site_admin":false},"created_at":"2015-01-29T15:37:13Z","updated_at":"2015-01-29T15:37:13Z","body":"Thus, unless you have a better idea, the only thing I can see is to give up on having a common handling for both mouse and keyboard, and use a this.list.on(\"click\") for mouse and the navigation events only for keyboard interaction."}}