You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2020. It is now read-only.
I just tried the latest nightly v2.0.1-67 and I was seeing a very strange behavior on a qtip with an ajax content component:
jQuery(this).qtip({content: {text: jQuery(this).attr('qtip-txt'),title: {text: jQuery(this).attr('qtip-title'),button: true},ajax: {url: MassMail.initParms.url_uiservlet,xhrFields: {withCredentials: true},type: "POST",data: {funct: "getusertip",cecid: jQuery(this).attr('qtip-txt')},once: true// only fetch the content the first time the tip is shown}},show:{event: "mouseenter",solo: false},hide: "mouseleave",events: {render: function(event,api){api.elements.target.bind("click",function(){api.set("hide.event",false);});},hide: function(event,api){api.set("hide.event","mouseleave","unfocus");}},style: {tip: true,classes: 'qtip-shadow qtip-rounded qtip'+jQuery(this).attr('qtip-cls')}});
The first mouseover everything is fine, but on the second mouseover it is making another XHR request, but without the "data" being passed, thus returning unexpected html content.
I rolled back to v2.0.1-37 and it's working correctly again.
The text was updated successfully, but these errors were encountered:
Happening to me with your jsfiddle. First request is a correct "POST http://fiddle.jshell.net/echo/html/" but all further requests are all "GET http://fiddle.jshell.net/fDavN/5919/show/" , thus returning the whole HTML, clearly visible in Firebug's console.
Tested with latest Firefox (19.0.2), latest Chrome (26.0.1410.64) and IE9.
I just tried the latest nightly v2.0.1-67 and I was seeing a very strange behavior on a qtip with an ajax content component:
The first mouseover everything is fine, but on the second mouseover it is making another XHR request, but without the "data" being passed, thus returning unexpected html content.
I rolled back to v2.0.1-37 and it's working correctly again.
The text was updated successfully, but these errors were encountered: