TicketSearch performance with Internet Explorer

Hi all, there’s some poor performance in Internet Explorer when you try to select multiple choices of one field in AgentTicketSearch. I’ll try to explain: let’s say you want to filter tickets in a, h, j, k, l, t, v, w and z queues. So you go to AgentTicketSearch; in there, you select ‘queue’, press the ‘plus’ button and you get a multiple-select with all your queues. then you press ‘control’ in your keyboard, because you want to select multiple non-adjacent queues, and start selecting queues by clicking on them with your mouse. When you have several queues selected, it takes several seconds to select another one, and these times get worst with every queue added. We’ve only seen this behaviour with Internet Explorer 6 to 8 (we know 6 is not supported, but we still have some apps that only work with it, so we must keep it); It is working OK with IE9, Chrome, Firefox, Opera and Safari. Has anyone seen this behavior? Kind regards, Juan Clavero

[snip – general suckitude of IE6-8] We’ve only seen this behaviour with Internet Explorer 6 to 8 (we know 6 is not supported, but we still have some apps that only work with it, so we must keep it); It is working OK with IE9, Chrome, Firefox, Opera and Safari. Has anyone seen this behavior?
Yeah. Nothing to do about it but upgrade the browser. IE6-8 had a number of perversions about how it handled this type of thing, and this happens to trigger one of them. If you keep adding queues, it'll eventually kill the browser.

Ok, thanks Bad news for the bosses, more or less what I expected.. and thanks for the "snip - suckitude"! great summary using a great word... Kind regards, Juan Clavero -----Mensaje original----- De: David Boyes [mailto:dboyes@sinenomine.net] Enviado el: lunes, 06 de agosto de 2012 11:47 Para: User questions and discussions about OTRS. Asunto: Re: [otrs] TicketSearch performance with Internet Explorer
[snip – general suckitude of IE6-8] We’ve only seen this behaviour with Internet Explorer 6 to 8 (we know 6 is not supported, but we still have some apps that only work with it, so we must keep it); It is working OK with IE9, Chrome, Firefox, Opera and Safari. Has anyone seen this behavior?
Yeah. Nothing to do about it but upgrade the browser. IE6-8 had a number of perversions about how it handled this type of thing, and this happens to trigger one of them. If you keep adding queues, it'll eventually kill the browser.
participants (2)
-
David Boyes
-
Juan Manuel Clavero Almirón