This module seems to assume that people are using a mouse. I had trouble using it to navigate to the individual panels of a keyboard when clicking through without my mouse.

Code like this:

 // Hide the contextual links when user clicks a link or rolls out of
// the .contextual-links-region.
$region.bind('mouseleave click', Drupal.contextualLinks.mouseleave);

Can we get the Mouse over mode to respect both the focus of the keyboard as well as the
<option selected="selected" value="mouseover">Mouse over</option>

Comments

mgifford’s picture

mgifford
he/him
Primary language English
commented

In looking at this again I wonder if the function _menu_minipanels_hover_defaults() just needs to have a secondary event added for when the panel should be shown.

I think this is what in the menu_minipanels module provides the array to qTip that defines its functionality. I don't know that onfocus is supported but there's some

    'show' => array(
      'delay' => 0,
      'when' => array(
        'event' => 'mouseover',
        'event' => 'onfocus',
      ),

Any thoughts on how to move this forward?

FranzSkaaning’s picture

FranzSkaaning commented

I am having similar thoughts. Onfocus should actually do it.
But even the Qtip2 library seems to not be too accessible. See the http://qtip2.com/demos and try tabbing through the page with the keyboard.
Maybe the real place to place a bug report or feature request is there...

The Qtip1 demos are even worse.

mgifford’s picture

mgifford
he/him
Primary language English
commented

Ok, posted a quick note here https://github.com/qTip2/qTip2/issues/646

Please add to it.