Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Currently, the "Use AJAX tooltip" option doesn't actually use any AJAX – instead, it will use an <iframe> as the tooltip contents which will then be loaded with the specified URL. This works pretty well for some use cases, but has the disadvantage that it becomes much harder to style the tooltip like an ordinary, text-based one. Also, styles and scripts will be sent along with the framed page, which can be desired, but might just slow things down at other times.
I therefore propose adding support for really retrieving the tooltip via AJAX. This would be another option if "Use AJAX tooltip" (which I would also label differently) is selected.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2894522-3--actual_ajax_support.patch | 10.82 KB | drunken monkey |
Comments
Comment #2
drunken monkeyThe attached patch would implement this. Please test/review!
(I implemented the new functionality using the qTip 1 library (since that's the one working with the jQuery version normally included in Drupal 7). Making it work with qTip 2, too, might need some additional adjustments.)
Comment #3
drunken monkeyUpdated patch, according to latest module commits.
Comment #4
joelpittetGood idea, could you maybe change the variable that was 'ajax' to 'iframe' so you don't have to use 'true_' prefix?
Comment #5
drunken monkeyThen we'd either have to have an update hook handling Views' internal config structure, or include BC code to handle the old option structure as well (especially difficult if the new variable is called the same as the old).
So, since most users won't care about the internal names anyways, I'd just leave this as-is.
But thanks a lot for your feedback! Glad to hear it sounds useful to you, too.
Comment #7
drunken monkeyCommitted.