{"action":"created","issue":{"url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/issues/68","labels_url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/issues/68/labels{/name}","comments_url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/issues/68/comments","events_url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/issues/68/events","html_url":"https://github.com/CWSpear/bootstrap-hover-dropdown/issues/68","id":38170308,"number":68,"title":"Touchscreen enabled Windows 8 behavior on Chrome 35.0.1916.153m","user":{"login":"guaka","id":54728,"avatar_url":"https://avatars.githubusercontent.com/u/54728?v=3","gravatar_id":"","url":"https://api.github.com/users/guaka","html_url":"https://github.com/guaka","followers_url":"https://api.github.com/users/guaka/followers","following_url":"https://api.github.com/users/guaka/following{/other_user}","gists_url":"https://api.github.com/users/guaka/gists{/gist_id}","starred_url":"https://api.github.com/users/guaka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/guaka/subscriptions","organizations_url":"https://api.github.com/users/guaka/orgs","repos_url":"https://api.github.com/users/guaka/repos","events_url":"https://api.github.com/users/guaka/events{/privacy}","received_events_url":"https://api.github.com/users/guaka/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":33,"created_at":"2014-07-18T12:04:07Z","updated_at":"2015-04-15T17:02:36Z","closed_at":null,"body":"It doesn't work on Windows 8 with Chrome 35.0.1916.153m"},"comment":{"url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/issues/comments/93487449","html_url":"https://github.com/CWSpear/bootstrap-hover-dropdown/issues/68#issuecomment-93487449","issue_url":"https://api.github.com/repos/CWSpear/bootstrap-hover-dropdown/issues/68","id":93487449,"user":{"login":"CWSpear","id":495855,"avatar_url":"https://avatars.githubusercontent.com/u/495855?v=3","gravatar_id":"","url":"https://api.github.com/users/CWSpear","html_url":"https://github.com/CWSpear","followers_url":"https://api.github.com/users/CWSpear/followers","following_url":"https://api.github.com/users/CWSpear/following{/other_user}","gists_url":"https://api.github.com/users/CWSpear/gists{/gist_id}","starred_url":"https://api.github.com/users/CWSpear/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CWSpear/subscriptions","organizations_url":"https://api.github.com/users/CWSpear/orgs","repos_url":"https://api.github.com/users/CWSpear/repos","events_url":"https://api.github.com/users/CWSpear/events{/privacy}","received_events_url":"https://api.github.com/users/CWSpear/received_events","type":"User","site_admin":false},"created_at":"2015-04-15T17:02:36Z","updated_at":"2015-04-15T17:02:36Z","body":"Issues with this approach:\r\n\r\nIt'd be best not to even *attach* the `mouseenter`/`mouseleave` (aka `hover`) listeners if the device is \"touch only.\"\r\n\r\nHowever, with this approach, we don't *know* on page load if the device `isTouchOnly`, so we can't really assume `isTouchOnly === true` on load like this approach assumes.\r\n\r\nThe best we can do is:\r\n\r\n```js\r\n$this.hover(function (event) {\r\n  if (isTouchOnly) return;\r\n  ...\r\n}, function (event) {\r\n  if (isTouchOnly) return;\r\n  ...\r\n});\r\n```\r\n\r\nVery messy and means we have a totally DOA event handler that the system has to listen to that literally does nothing.\r\n\r\nBefore someone suggests it: I'm *not* okay with putting in some sort of timeout check to wait to see if we get a `movemouse` event. It's possible someone doesn't move their mouse (thus triggering the `mousemove` event) for a while, and it'd be *so* hard for the end-developer to debug this if they didn't know it was there. And users could potentially see differing behaviors that would be very frustrating.\r\n\r\nBut at this point, I don't know what else we could do, and the cost of an event handler on today's phones is not going to probably causes issues in the vast majority of situations.\r\n\r\nSo again, to reiterate: we need to know if the user has a mouse, and if they don't, don't even activate this plugin at all. But we don't have any way of knowing they have a mouse unless they use it, so our base assumption has to be \"no mouse\" which creates a contradiction of sorts."}}