Why I Moved to WordPress

I wanted to display a hidden image in the “almost daily rag” post. I wanted this image to only appear when a highlighted keyword was clicked, pushing content above and below it neatly out of the way. Then when the visitor clicked on the image, it would return to being hidden and everything would size back to normal.

So I slipped a little HTML and JavaScript into the post to accomplish that task. I was testing this in Firefox and surprised myself by how quickly I got it to work (cocky idiot).

The next step was to test it in Internet Explorer, where sure enough, a glitch occurred. But I lucked out and was able to tweak the code a little bit to fix it, and when I retested in Firefox it was still OK there as well.

Later in the day I tested it on my iPad, in Safari – no go. Got ugly. Same with an addin browser app called Terra on the iPad. And my phone? No, uh-uh. And in the versions of IE at the plant? Surely not OK there either. No go in Chrome – on any platform.

So I ended up deleting the day’s entry, and the image, and the special HTML and JavaScript. At first I was irritated about it all but soon the light bulb came on. That’s why I moved to Word Press. To get out of the browser wars. WordPress takes care of all that. As long as you use stay with the features provided, and do same with the themes, it’s all good.

Putting together a web site from scratch means needing to test what browser you’re running in (and what version no less) and what platform you’re on, followed by having to code a few routines and HTML sequences a different way. Or possibly decide that if it’s this or that browser, I just won’t have this feature I want at all? Ugh.

Call me lazy if you like. But with the browser creators all doing their own thing and most ignoring some parts of the W3C HTML RFC standardization specifications, and the rapidly growing world of unique platforms, it just gets old. Like me I guess.  :)

<span>%d</span> bloggers like this: