Acceptance Tests

[CWSpear]

As part of #69, in addition to some tests with Karma, etc, we really need some solid Acceptance Tests to handle cross browser quirks.

Specifically, the issue(s) plaguing us:

• Mobile devices: Mobile devices don't have hover events. We want mobile devices to only activate dropdowns on touch. Furthermore, we need to consider how we want to handle "clicking" on the parent in these scenarios (a highly requested feature. See Is it possible to make the parent clickable #27 and Question re: making parent menu links clickable #16).
• Touch enabled desktops: As per the last issue, it isn't enough to disable hover events if the devices has touch events, because Windows 8 desktops have touch enabled and still have a mouse. We want these dropdowns to work on hover.
• Cross browser/device quirks: For example, I haven't been able to verify, but I've gotten multiple reports of weird stuff going on on Windows Phones: Menus automatically closing on Windows Phone 8 #28

[CWSpear]

I have a BrowerStack account that we can use for testing.

[CWSpear]

I'm not 100% sure, but Pointer Events (à la jQuery's PEP) may help. All major browsers except Safari have recently committed to implementing this natively (i.e. see this thread).

(Note, this is not the same thing as pointer-events: none; (well, actually, I think they may be related, but it's much more than just that). See the PEP thing for more, but it's a series of events that should better handle issues with click vs touch.)