Blog

jQuery tabs and IE caching...

Curt Gratz February 02, 2010

Spread the word

Curt Gratz

February 02, 2010

Spread the word


Share your thoughts

I ran into an interesting issue using the jQuery UI tabs ajax style and Internet Explorer. 

If you setup the tabs with the with the cache turned off, they will still be cached in IE.   I had worked around this issue by adding a counter that changed every time to my href for the tab, but I found a more elegant solution and thought I would share.

 $(document).ready(function(){

$("#tabs").tabs({ 

spinner: 'Loading...',

cache: false

});

});

The solution for this is to not only set the cache to false, but also to use the ajax options and set cache to false there also.  So the code would change to this...

 $(document).ready(function(){

$("#tabs").tabs({

spinner: 'Loading...',

cache: false,

ajaxOptions: {cache: false}

});

});

Add Your Comment

(5)

Jul 19, 2010 05:40:01 UTC

by göran

Ok, but in which context? Are you using coldbox 3, coldbox 2.6.4 or? Are you using CF8 Server, CF7 or OpenBD or are you just using JQuery and IE?

Jul 19, 2010 05:56:20 UTC

by Curt Gratz

Not a ColdBox or ColdFusion issue at all. It is purely an IE and jQuery issue. IE 6,7 & 8 and jQuery 1.3.2.

Curt

May 31, 2011 19:48:46 UTC

by Carlos Alvarado

Thank you, works like a charm =)

Jun 01, 2011 16:44:20 UTC

by Scott Smith

You are the man, thanks! This is definitely just an issue with IE and jQuery and still exists in later versions than 1.3.2 as well.

Mar 14, 2012 14:58:25 UTC

by Alexander

do not work with IE9

Recent Entries

BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

BoxLang 1.17 Series Part 4 : WriteDump Enhanced!

You call writeDump() on an ORM entity or a very rich class graph . The browser locks up. Thirty seconds later you get a page with forty thousand rows on it, you scroll for a while, you give up, and you go edit your code to dump a sub-key instead. Or worse, you crash the server.

Luis Majano
Luis Majano
September 11, 2026
BoxLang AI 3.4 Blog Series Part 4 : Locking Down Prompt Injection

BoxLang AI 3.4 Blog Series Part 4 : Locking Down Prompt Injection

LLM applications face a class of attack traditional input validation was never built for: prompt injection. An attacker embeds instructions in user input, a retrieved document, a web page your tool fetched, or an MCP result, trying to override your system prompt, exfiltrate data, or hijack a tool call. BoxLang AI 3.4.0 ships four layered, configurable defenses against exactly this, plus one more that's on unconditionally.

Luis Majano
Luis Majano
September 11, 2026