Comments on: cloneNode caching http://verens.com/2006/01/09/clonenode-caching/ klog - Kae's Log Mon, 21 May 2012 21:11:58 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Yongchun http://verens.com/2006/01/09/clonenode-caching/#comment-591 Yongchun Tue, 17 Jan 2006 14:03:24 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-591 Spam? It makes me laugh. I wrote it personally for your attention. In that IE thread, there are 160 replies.  I think it is more proper to directly to the person to whom we may give help. Spam? It makes me laugh. I wrote it personally for your attention. In that IE thread, there are 160 replies.  I think it is more proper to directly to the person to whom we may give help.

]]> By: Kae Verens http://verens.com/2006/01/09/clonenode-caching/#comment-590 Kae Verens Mon, 16 Jan 2006 21:00:10 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-590 interesting... I don't know whether to mark that as spam or not - it's a reply a post I made here: http://blogs.msdn.com/ie/archive/2006/01/12/512232.aspx I have no idea why Yongchun didn't reply in that original thread. interesting… I don’t know whether to mark that as spam or not – it’s a reply a post I made here: http://blogs.msdn.com/ie/archive/2006/01/12/512232.aspx

I have no idea why Yongchun didn’t reply in that original thread.

]]> By: Yongchun http://verens.com/2006/01/09/clonenode-caching/#comment-589 Yongchun Mon, 16 Jan 2006 17:46:15 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-589 Kae, I saw the post on IE blogs about clear CSS and Javascript cache via reload. Our browser Tablane browser which is a shell based on IE, can help a bit. We don't have straight way to do that, but it is much quick than IE. Every time you want to reload a page, just create a new Tab using the same URL. (You can delete all other Tab except current on in one go) Here is the procedure: In Tablane Top Toolbar, click the little triangle beside the New Tab icon, choose Current Page. Every time, you create a Tab, it will load current URL in New Tab(this will reload CSS and Javascript). Ctrl+T will create a New Tab. Hope this will help. Download from www.tablane.com Kae,
I saw the post on IE blogs about clear CSS and Javascript cache via reload. Our browser Tablane browser which is a shell based on IE, can help a bit.
We don’t have straight way to do that, but it is much quick than IE.
Every time you want to reload a page, just create a new Tab using the same URL. (You can delete all other Tab except current on in one go)
Here is the procedure:
In Tablane Top Toolbar, click the little triangle beside the New Tab icon, choose Current Page. Every time, you create a Tab, it will load current URL in New Tab(this will reload CSS and Javascript).
Ctrl+T will create a New Tab.
Hope this will help.
Download from http://www.tablane.com

]]> By: Kae Verens http://verens.com/2006/01/09/clonenode-caching/#comment-588 Kae Verens Wed, 11 Jan 2006 09:13:16 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-588 I have updated the post to include a more optimised version which checks for the browser type before it creates the function. I have updated the post to include a more optimised version which checks for the browser type before it creates the function.

]]> By: Kae Verens http://verens.com/2006/01/09/clonenode-caching/#comment-587 Kae Verens Wed, 11 Jan 2006 06:47:14 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-587 Safari uses a version of the Konqueror engine, so I am not surprised about that. Maybe the performance increase is only evident in IE and Firefox (the dominant browsers anyway). Safari uses a version of the Konqueror engine, so I am not surprised about that. Maybe the performance increase is only evident in IE and Firefox (the dominant browsers anyway).

]]> By: Uili http://verens.com/2006/01/09/clonenode-caching/#comment-586 Uili Tue, 10 Jan 2006 18:16:41 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-586 on Safari 2.0.1 test 1 was 973 ms and test 2 was 1043 ms, I am not sure which is ment to be faster but though I would post the results in case they where of intrest. on Safari 2.0.1 test 1 was 973 ms and test 2 was 1043 ms, I am not sure which is ment to be faster but though I would post the results in case they where of intrest.

]]> By: Kae Verens http://verens.com/2006/01/09/clonenode-caching/#comment-585 Kae Verens Tue, 10 Jan 2006 12:48:36 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-585 I had noticed the konqueror result (and wondered if it was a bug to be reported). Didn't know about Opera, though - I'll see if I can tweak it to be faster all-round. Maybe a customised function using a technique like <a href="http://dean.edwards.name/weblog/2005/12/js-tip1/" rel="nofollow">this one</a> so there is no performance loss through browser-checking. I had noticed the konqueror result (and wondered if it was a bug to be reported). Didn’t know about Opera, though – I’ll see if I can tweak it to be faster all-round. Maybe a customised function using a technique like this one so there is no performance loss through browser-checking.

]]> By: Christof Donat http://verens.com/2006/01/09/clonenode-caching/#comment-584 Christof Donat Tue, 10 Jan 2006 12:42:32 +0000 http://verens.com/archives/2006/01/09/clonenode-caching/#comment-584 In Firefox and IE your new function is faster than the old one, but not in Konqueror and Opera. In case you do further initialisation with your nodes, I would expect the new function to win. In Firefox and IE your new function is faster than the old one, but not in Konqueror and Opera. In case you do further initialisation with your nodes, I would expect the new function to win.

]]>