Bug Tracker

Custom Query (13852 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 13852)

Ticket Resolution Summary Owner Reporter
#11243 invalid AJAX requests (e.g. calling $.get() or $.ajax()) sometimes fail without calling any of the callback functions CrazyChoco CrazyChoco
Description

Hello there

We usually like to be quite bleeding edge when it comes to jQuery releases, and we've been trying out jQuery version 1.7.1 for just over a month now for our AJAX-based applications.

Unfortunately we are occasionally seeing a problem when using jQuery to launch AJAX requests.

Occasionally a request will fail for some reason (which may be legitimate, e.g. due to a network issue or timeout). However sometimes jQuery will then not call the "success" function it was passed, *and* not call the error handler function registered by $.ajaxSetup(). This effectively causes an AJAX-based application to "stall", as without the success function or the error-handler being called to let it know that it can continue, it just sits there waiting.

This event seems very rare (definitely less that one time in 100) but can be reproduced eventually by sitting down and using an application for long enough. By adding debug information we have narrowed the problem down to the calls to $.get() and $.ajax(), and are reasonably confident that it is a problem with the error handlers not being called.

Nobody can remember these problems happening in jQuery 1.6.4, so we suspect it may be a reasonably recent problem.

#13506 wontfix stopPropagation behaviour when trigger is passed an event. [email protected] [email protected]
Description

The stopPropagation behaviour is very unexpected when passed an event object. I believe it works incorrectly whereas the behaviour is correct when passed an event name.

Pass an event Name - works as expected


function someFunction(event){
    event.stopPropagation();
}

$('#object1).on('customEvent', someFunction).addClass('customEventClass');
$('#object2).on('customEvent', someFunction).addClass('customEventClass');

$(".customEventClass").trigger('customEvent');


As expected both object1 and object2 will have the function 'someFunction' called, but the event won't bubble up the DOM tree.

Pass an event Name - very unexpected behaviour


function someFunction(event){
    event.stopPropagation();
}

$('#object1).on('customEvent', someFunction).addClass('customEventClass');
$('#object2).on('customEvent', someFunction).addClass('customEventClass');


var event = jQuery.Event('customEvent');
$(".customEventClass").trigger(event);

Only one of the objects will receive the event. I expected both of them to receive the event.

The problem appears to appear to lie in the code

"while ( (cur = eventPath[i++]) && !event.isPropagationStopped() ) {"

in the function "trigger: function( event, data, elem, onlyHandlers )"

The event object is passed in to this function and so on to the callback function for the first object, which calls event.stopPropagation() on the object, which sets the prototypes function "isPropagationStopped" to "returnTrue"

On the second (and subsequent) calls to "trigger: function( event, data, elem, onlyHandlers )" the event object still has "isPropagationStopped" set to "returnTrue" and so it doesn't actually get triggered for the rest of the elements.

I think the stopPropagation behaviour should be the same for when trigger is passed an event object, as when it is passed a string.

#12773 notabug slideDown() bug changes "display" property of child elements; slideUp does not [email protected] [email protected]
Description

slideDown() changes "display" property of child elements.

This is unwanted! (I am the programmer. I know which element I want to slideDown. If I wanted any child elements to be changed I would call slideDown on them, and I DO .. IF I want the child element shown. The parent is a <UL> list of forum topics, the children are <LI> topic links, some unread, some read. The display or hiding of topics already read, are handled separately from the show all/hide all of the parent <UL>.)

When I call slideUp on the parent <UL> it leaves all the child <LI> elements "display" properties as I have them set (ie, only the unread topics showing.) This IS expected behavior.

When I call slideDown on the parent <UL>, I expect it, and ONLY it's "display" property to be set "block", which should reveal the list but NOT touch the child items. The list should display as it was when I hid it with slideUp.

PC - Windows XP Google Chrome 22.0.1229.94

Note: See TracQuery for help on using queries.