Come on now. You take a lot of pride in your plugin, don’t you? Take the same pride in the code that it generates. I take pride in my web design. I want my sites to validate as to both CSS and HTML. But your silly little plugin is riddled with errors and, quite frankly, sloppy CSS. Why just look here (this is just a sample; your plugin actually generated over 50 CSS errors!):
65 .ec3_ec attempt to find a semi-colon before the property name. add it 65 .ec3_ec Property progid doesn't exist : DXImageTransform 66 .ec3_ec Parse error - Unrecognized } 72 #ec3_shadow0 div attempt to find a semi-colon before the property name. add it 72 #ec3_shadow0 div Property progid doesn't exist : DXImageTransform
And just so you don’t think I’m picking on just one plugin, here’s more:
48 * html #TB_overlay Value Error : height Parse error - Unrecognized } 65 * html #TB_window Value Error : margin-top Parse error - Unrecognized }
Bottom line here? If you can’t be bothered to create solid CSS, how can I trust your code?
Joni Mueller has been designing web sites for hire since 2003, when she first blew up her web host’s server by insisting on running Greymatter. Since then, Joni has designed for Blogger and Movable Type, TextPattern, WordPress and CMS Made Simple. She lives with her cat and shoe collection in a bucolic old section of Houston called Idylwood. For some strange reason, Joni likes to refer to herself in the third person. When she’s not working on web design, she’s ordering lawyers around. And blogging about it. Or both.