Allow users to click on links within default text input beautytips

Whether this is a bug or not depends on how you've setup beautytips. Is this using the built in text input tips or custom tips?

If you're using a custom beauytip, then this information may be helpful.
If the tips are set to show up on hover, then they'll disappear when a user is not hovering over the trigger item. Alternatively, you can set it up to only disappear on a mouse click. Or, you can also use hover intent, which allows the beautytip to have a timed turnoff.

I had never really tried doing that, but you're right it doesn't work. The 'blur' event, which turns the beautytips off, runs before the mouse click is registered, so you end up clicking on whatever was behind the tip.

I'm going to move this to a feature request. It's probably a matter of playing around with the different possible triggers for turning the tips on and off. If that doesn't fix it, then it would need to be fixed in the beautytips plugin itself.

For now, I suggest just copying the code that creates the text input beautytip and play around with the possible triggers to see if you can find a combination that meets your needs. It's really a matter of how you decide the beautytips should be turned off. If you find something that works for you, then let me know.

[edit]
Actually, just tested this out and found that it works well for link clicking if you set the off trigger to 'dblclick', plus it seems to turn off on blur anyway. Anyway, that may work for you.

Hi kleinmp -
When you were testing this out, do you remember where/how you set the trigger to dblclick?

I copied the code form the textinput.inc that adds the options to the node form. Then I changed the trigger to use dblclick instead of blur.

...
$options['bt_text_field'] = array(
  'cssSelect' => 'input.form-text',
  'trigger' => array('focus', 'dblclick'),
  'contentSelector' => "$(this).nextAll('.description:eq(0)').hide().html()",
  'width' => '275px',
  'positions' => array(0 => variable_get('beautytips_position', 'bottom')),
  'preEval' => TRUE,
);
...

Thanks for the quick response - I ended up finding that chunk of code and changing the trigger worked, but I'd rather not patch the module. Is there a way I can edit these settings from a form alter?

I'm thinking about making the show and hide events configurable on the settings page. For example, under the Text Input Tooltips fieldset I will add 2 pairs of select lists - one for text field and one for text area. Each pair will have 2 drop downs. One drop down would be for the "show" event and one for the "hide" event, both with some help text. Both select fields would contain a list of jQuery events relevant to text input fields.

Would you consider accepting this patch if I work on it? I may have time for it tonight.

As mentioned above, this patch adds two sets of fields to give show/hide events for text fields and areas. I chose focus, blur, and dblclick as the possible events. Though not all of the events make sense together - for example, blur for show combined with focus for hide :) - none of the combinations are harmful and the defaults (same as before) work great. Let me know if there are any tweaks and I can re-patch.

It appears you have removed all of the t() code which is vital for international multi language sites. I'll try to patch manually without these changes and test to let you know.

Strange - I'm surprised I didn't notice that. Thanks for the heads up. Let me know if it works and I can re-patch with t() included.

Added t() calls back.