Framebreak
There's a line of javascript for making sure that framed pages can't be called outside of their frames. This happens more often than we think because spiders are indifferent to context (and coder's intent), the result being googled content with no indication of where they properly belong. Outside the frame, any file--whether it's about cold beer or cold fusion--is just one of gazillions of URLs floating out there.
Another less serious thing that can go wrong with frames is that, if the coder isn't mindful of target tags, external links could find themselves trapped inside the frame. Some really nice websites get ruined for me that way. Conversely, it also bothers me when I place an external site like, say, from Blogger inside frames. It bothers me even if it's my own account.
I meant for this page to be part of my top-secret portfolio site umbrella+sewingmachine and so I wanted a unified design. Php was my first choice but since I didn't have time to revive my domain and couldn't wait to start, frames were the obvious no-brainer. But it just kept niggling at me, framing this page and so, this morning, I set it free. I'm pretty sure, however, that nobody will notice because (1) it still looks exactly the same, pixel for pixel, onload, and (2) nobody's reading this, anyway.
But changing one page means having to change the others and that's what I'll be doing for the rest of the day. Widget testing, too. And maybe footnotes.
