Categories
Computing Web Development

IE border rendering bug

Another Internet Explorer bug for the books:
Create a <div> element and give it a border, something like:

div.product_intro
{
border-width: 0.1em 0.1em 0em 0em;
border-style: solid;
border-color: #ccc;
padding-top: 0.7em;
padding-right: 0.7em;
padding-bottom: 1em;
}

You would expect it to look something like this.

Now scroll down the page so that the div is obscured and outside your viewport (the broswer no longer shows it).

Scroll back up.

This is what I got. Where did they border go?

The fix (so far): Set the width for the div explicitly. That also cures another outrageous bug where IE pushes divs around the aforementioned div with irrational spacing.

Share
Categories
General

Jill and Yuval’s Monster Truck Experience

It was my first weekend away with Jill and a beginning of a great relationship. Jill, me, monster trucks. We have yet to experience the noise and thunder again. The photos convey too little of the noise, the smells, the happening. It was just really cool.

Monster Trucks, Providence, RI, January 2003.

Share
Categories
Computing Web Development

PHP 4 Stinks – Reason Number 3008

PHP sucks ass in a tremendous way.

So I am parsing an XML file with PHP.
The xml file has an element like:
<element>this-is-the-data</element>

Any language worth two cents would return the CDATA of this element as:
this-is-the-data

But PHP – no.

Its native parser – a really fast SAX parser – calls the CDATA handler multiple times, but not in a consistent fashion (for real) – so you cannot just use a call like
$x = $data;
where $x is some variable and $data is the character data the event returned. This will occasionally overwrite $x with the current partial data returned from the parser.
You must use
$x .= $data
which means – “append to $x”.

How f-n stupid is that?! And is this documented ANYWHERE?!!!!!
No.
PHP is enterprise ready like Clay Aiken is straight.

Share
Share