http://www.mooreds.com/wordpress/archives/489 Tue, 07 Feb 2012 14:11:43 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.mooreds.com/wordpress/archives/489/comment-page-1#comment-2289 moore Wed, 08 Oct 2008 18:25:45 +0000 http://www.mooreds.com/wordpress/archives/000489#comment-2289 To be fair, I don't think it is entirely Wordpress's fault. I think it's how they configured <a href='http://tinymce.moxiecode.com/' rel="nofollow">TinyMCE</a>. In digging around, the Wordpress Team seemed to have reasons (rendering issues) for doing this. To be fair, I don’t think it is entirely WordPress’s fault. I think it’s how they configured TinyMCE. In digging around, the WordPress Team seemed to have reasons (rendering issues) for doing this.

]]> http://www.mooreds.com/wordpress/archives/489/comment-page-1#comment-2288 Brett Borders Wed, 08 Oct 2008 16:36:24 +0000 http://www.mooreds.com/wordpress/archives/000489#comment-2288 I'm not using WP 2.3, but this problem has driven me CRACKERS before. "What part of DIV don't you understand. .freakin #$@#$ Wordpress~!!!" I’m not using WP 2.3, but this problem has driven me CRACKERS before. “What part of DIV don’t you understand. .freakin #$@#$ WordPress~!!!”

]]>