Touch + Mouse enabled Windows

[guaka]

It doesn't work on Windows 8 with Chrome 35.0.1916.153m

[donquixote]

The "open" class is not added.
Nothing special showing on the console.
Tried http://cameronspear.com/demos/bootstrap-hover-dropdown/, doesn't work either.

[cheesington]

I'm getting the same thing. I think the problem is that touch is enabled in windows 8, and chrome is registering itself as a touch-enabled browser. Line 22 detects this and ejects without adding the hover functionality:

if('ontouchstart' in document) return this; // don't want to affect chaining

I'm not sure what the answer is, but I'm fairly sure this is the problem.

[tszming]

@cheesington do you mean on a Windows 8 PC without touch support but Chrome think it is a touch enabled browser? Then it is a Chrome's bug.

On the other hand, how about on a PC with touch + mouse support, can this plugin handle this case?

[cheesington]

@tszming: You know, that's a good point. It's possible that chrome on a touch-enabled windows 7 computer would exhibit the same problem -- my assumptions about windows 8 are based on the previous comments and experience with my touch-enabled windows 8 machine, and could be overly specific.

I can say that my computer has both touch and mouse support, and exhibits the problem.

[donquixote]

Hi.
I am only reporting in 3rd person, but from the information I get, I would confirm that the touch thing is the right direction to investigate.
There are two scenarios:

1. A machine which has touch and mouse. E.g. a touch-enabled laptop with a mouse connected.
2. A machine which has only mouse, but which behaves as if it also had touch.

We should have a sensible behavior for both.

[CWSpear]

It makes sense that it's what @cheesington is pointing out, but removing it isn't necessarily the answer.

The over-arching issue here is we want it to be disabled on a device that you would use touch on, as it interferes. The problem being hybrids, i.e. Surface Pro w/ Windows 8.

[CWSpear]

Oh, and I don't have Windows 8, so testing it is slightly nontrivial for me. I know there are ways, but I don't have anything set up.

[guaka]

On this win8 laptop with touchscreen I get:

Chrome ('ontouchstart' in document) == true
Firefox ('ontouchstart' in document) == false
IE ('ontouchstart' in document) == false

I'd like to add some code that continues with the hover code anyway if it's a desktop or laptop machine and not a tablet or mobile phone.

[CWSpear]

@guaka Do you have one of those Surfaces or other touchscreen-enabled laptops?

Several solutions have been proposed to fix those. I really don't like the approach of looking at the screen width as the breakpoints are customizable. But I dislike #75 the least, so I am considering an approach like that one.

[guaka]

I only have one Windows 8 machine, with touchscreen and keyboard.

Screen width should not be a factor ideally.

[CWSpear]

What should be the factor then?

[guaka]

I'm reading this interesting and highly relevant SO question now:
Detecting that the browser has no mouse and is touch-only

On Fri, Aug 22, 2014 at 7:09 PM, Cameron Spear notifications@github.com wrote:

What should be the factor then?

—
Reply to this email directly or view it on GitHub.