Written By: EMG
Posted On: Aug 22, 2010
Filed Under: In the Studio, On the Web Design Front, On the Web Development Front, On the WordPress Front
I’ve been working on a fully fluid-width, XHTML Strict, table-less, three column child theme for WordPress’ Twenty Ten default theme…
And in the process, discovered a bottom margin bug!
I submitted the bug to a Trac ticket HERE and also documented the fix that would squash the bug flat and make Twenty Ten render the way it was supposed to which I will share here in my blog.
The Bug (in short):
The margin-bottom: 20px that is applied to the footer div triggers a well known CSS bug causing the 20px margin to be applied to the adjoining/bottom margin-touching wrapper div instead of the footer div.
That bottom margin you see at the bottom of the page where the end of the content wrapper should be touching the bottom of the screen?
That’s the bug.
The Fix (in short):
To correctly apply the 20px margin-bottom to the footer div and not accidentally to the wrapper div, the wrapper div needs to be given a 1px padding-bottom and the footer div needs to be given a 19px margin-bottom.
The padding applied to the wrapper where it touches the bottom of the footer container will trigger the margin-bottom to be rendered correctly for the footer and not the wrapper as the padding will add some ’separation’ between the two containers.
Another fix is to add a 1px border to the bottom of the wrapper and leave the 20px margin-bottom on the footer.
The border adds ‘content’ to the bottom of the wrapper which triggers the margin-bottom for the footer to be rendered correctly.
Why the Bug Happens:
Read the rest of this page »
Written By: EMG
Posted On: Mar 04, 2010
Filed Under: In My Mind, In the Studio, On the WordPress Front
… to the WordPress community.
So I was reading Andy Peatling’s post on giving back to the community in regards to open source projects (like WordPress, BuddyPress, bbPress, etc) and it got me thinking.
How have I given back to the WordPress (and other similar) communities?
Read the rest of this page »
Written By: EMG
Posted On: Jul 19, 2009
Filed Under: Administration, On the Web Development Front, On the WordPress Front
So uhmmm… whooops?
EDIT: Justin Thorp from the AddThis team directly replied to this post in a comment and said that the team is looking into resolving both issues! Thank you, Justin! 
The newer version of the WordPress-specific AddThis coding (the one you can manually add to your posts that uses the php echo?) does NOT validate through W3C. It WORKS, but because of the ampersand and perhaps something else, W3C is going bonkers over it, offering up anywhere between 5 to 9 errors on account of it.
So if you visit the blog and validate it and see a million AddThis validation errors? That’s why.
And oh yes, the ‘Print’ functionality does not work for a single post if you have the AddThis coding enabled on say your main blog page where it appears multiple times – once on each post.
Instead of printing that one post, it will print the entire page – whooops!
I hope AddThis fixes that soon!
~ EMG
Written By: EMG
Posted On: Jul 17, 2009
Filed Under: In My Mind, In the Studio, On the Web Design Front, On the WordPress Front
In some ways, Emotiomental Graffiti doesn’t look like much.
To be sure, it really isn’t all that complicated of a website compared to a lot of larger, more media-heavy, and more complex sites.
Running off of the (absolutely kick ASS) WordPress application (version 2.8), Emotiomental Graffiti is, for the most part, a smorgasbord of valid XHTML Strict coding (my work), WP-specific PHP hooks (their work; I just hitched it all together), and a crapload of CSS (my work).
Read the rest of this page »
