Object doesn't support this property or method in IE8

[Roshan Budhathoki]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET4.0C)
Timestamp: Wed, 2 May 2012 12:17:22 UTC

Message: Object doesn't support this property or method
Line: 1
Char: 11658
Code: 0

[Simo Kinnunen]

Hi,

Cufón sometimes has trouble when you give it native elements or jQuery objects. When using native element, do this:

Cufon.replace(this, { .. options .. }, true);

The last parameter makes sure that Cufón doesn't try to store the element for Cufon.refresh (which should be the source of the error). Alternatively, just use a selector.

Also, instead of

Cufon.replace($('selector'), { .. options .. });

you should use

Cufon.replace('selector', { .. options .. });

instead.

Also, note that if you load Cufón near (and you also have your replace calls there), plus you're wrapping the calls inside $(document).ready(), you will get a delay no matter what. If this is not an issue, do as you please. If it is, please read the FAQ. In essence, you will have to:

1. load cufon-yui.js and any font files in
2. have all replace calls in , or in a script file that is in
3. have Cufon.now() at the bottom of the page, BEFORE you start loading other scripts

If you do 1 and 2, you can also use the .cufon-loading CSS class to temporarily hide certain elements. More about that in the FAQ.

Simo

On May 2, 2012, at 9:34 PM, developerroshan wrote:

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET4.0C)
Timestamp: Wed, 2 May 2012 12:17:22 UTC

Message: Object doesn't support this property or method
Line: 1
Char: 11658
Code: 0
http://www.js.purlfrost.co.uk/content/themes/default/js/cufon-yui.js.php

Original Product Link: http://www.purlfrost.co.uk/house-numbers/contemporary-designs_1/hnc-4/

---

Reply to this email directly or view it on GitHub:
#244