Annoying CSS issue and solutions

We know that using CSS and DIV elements is the most versatile way to layout a web page. But when you drop tables you lose the browser’s native ability to resize elements properly when the user changes the window size, views on a mobile device, or changes the font size.  Eli details some of the common problems on his blog.

One situation I was getting annoyed with is setting up a horizontal link bar, much like you’d find in the header of many websites.  If you set all the elements to float left, you have to manually specify a height of the overall horizontal UL or DIV that encapsulates the floating elements. This is fine, except if you don’t know if the floating elements will fit inside a page width.  You might want the floating elements to spill over to the next line, and appropriately push the content of the page down.

I haven’t figured out how to do this using just DIVs and CSS. But I found if you wrap the horizontal bar in a table/tr/td, the table will automatically expand to contain all the floating elements, effectively giving the whole thing a proper height. This way you can set a background on the table and it will always be shown.

View the HTML example of this problem: Floating Element Test

New TypeMatrix 2030 Ergonomic Keyboard

I recently purchased and received my new TypeMatrix 2030 USB (2009 model) keyboard!  For those that don’t know, TypeMatrix is a company that produces what I believe to be the best, most comfortable and most logical keyboards that one can buy.  The version I bought is Dvorak, since that has been my preferred typing layout since around 2003.

The TypeMatrix 2030 USB (2009 Model) – Shown with Qwerty layout

What is even more pleasant is that… Continue reading Hacked!

I’ve been cleaning up a lot of crap over the past few days that was the result of an exploit on the site. Basically, most if not all “index.php” files in the directories of the site had various lines of advertising & link code inserted into them. They were inserted into hidden HTML elements so they couldn’t be seen unless you viewed the source.
At first I tried to figure out how the exploit was executed… WordPress? Gallery2? I wasn’t too sure so I removed all the spam links and javascript code and thought I removed access to the Gallery applications. But that wasn’t enough, as the next day I checked it, all the index files had been tampered with again. “Did someone get my password? How could this happen!” I thought. Then I realized there was still an old Gallery2 directory ready for exploiting. So I got rid of that promptly and cleaned up the whole site again.
I even re-installed WordPress to the latest version. My next steps are to install a backend for the site which would alert me via e-mail if certain actions occur.