It seems that the notoriously tightwad ICANN is now relaxing domain naming conventions. Now any combination of letters, numbers and non-Latin text will be able to resolve to a Web site. Personally, I think this is a serious mistake.

There already are plenty of domain name suffixes to select from but time and time again .COM is the most selected suffix. It’s what people know and they are used to. I remember a few years ago there was a huge stink over whitehouse.com going to a porn site rather then to a government site. Those who understood domain names would have gone to .GOV. At the time there were only a handful of suffixes to choose from, this new direction by ICANN will change all that.

Personally, I think this adds more confusion to domain names. I already see plenty of challenges, even with technical folks understanding the differences in subdomains such as blog.imulus.com vs imulus.com vs www.imulus.com. Usually there is a 50 / 50 chance that if I give someone a domain name containing a subdomain they will usually add www to the URL; for instance bet.rmi.org then becomes www.bet.rmi.org.

This will surely benefit search engines more then the average user. I guess the lawyers benefit also because it sure will be interesting to watch the copyright and trademark lawsuits for all the domain name variations which will be gobbled up by the name registers.

Nice move ICANN!

Months ago when working on development for RMI | BET’s video website I needed a way to do image rollovers but I didn’t want to have a reliance on javascript. So, I set out to a create a reusable image rollover solution that was completely CSS based. Basically the concept was to have a universal class that could be called at any time in the HTML to create a rollover image.

Since first creating this code I’ve integrated it as a standard into all of our starting CSS templates.

Here’s how this works:

Start out with a basic anchor tag and give it a class of “hover-box”. Then inside the anchor tag add both images, your original and your hover version. Place the hover image first in the tag, and then add the original one second. Add a class of “hover” to the hover image. It should look like this:

<a href="#" title="Link title..." class="hover-box">
   <img src="rollover-image.jpg" class="hover" alt="Rollover"/>
   <img src="original-image.jpg" class="original" alt="Original"/>
</a>


Now, make sure this CSS is included in your document.

a.hover-box img.original { /* required for IE6 */
    float: left;
    position: relative;
}
a.hover-box img.hover {
    display: none;
}
a.hover-box {
    position: relative;
    float: left;
    display: block;
}
a.hover-box:hover {
    display: block;
    font-size: 100%;
    z-index: 1;
}
a.hover-box:hover img.hover {
    display: block;
    position: absolute;
    left: 0;
    top: 0;
    z-index: 1000;
}

Okay, basically this is hiding the hover image to begin. Then, once the anchor tag is hovered over the image with class “hover” displays itself as block and is positioned absolutely directly on top of the original image. This is accomplished because the hover-box class is set with relative positioning, meaning that the hover image is tied to its boundaries.

Bang! There you have it, a simple CSS hack-free solution that works in: Firefox, Safari, IE 6 & 7, and presumably all other standards compliant browsers. Check it out in action…

P.S. This is especially sweet because the image is preloaded and then hidden, meaning the hover effect is instant for the viewer.

Edit: After some testing I found out my original version wasn’t always working in IE6. It seems that for some reason IE6 needs a class applied to the original image that floats it and positions it relative. I tried every possible way and this is the only thing making it work without a * hack. Not a huge deal though. Also, IE6 requires the original image to come second in the HTML, unlike I originally thought.

Looks like today at the SXSW conference in Texas the Internet Explorer team made a surprise announcement that IE8 beta 1 is available for public download. Right now.

That’s right, the standards compliant, new version of IE is out for public testing and use as we speak.

I really have to say, over the past few months of reading the Microsoft IE blog I’ve been impressed with their change in attitude. This release of IE8, ahead of schedule just goes to further my appreciation of their new approach regarding developers and users.

I’m also personally excited to see continual development and advancement in the Microsoft browser space. The sooner IE8 goes live via Windows update the better. Hopefully within a year or so IE6 will be a memory of the past and developers can finally start to utilize PNG graphics and advanced CSS to the fullest.

About a month ago I posted a blog about Internet Explorer 8 (which recently passed the Acid 2 web standards test) requiring a special tag to utilize its new web standards rendering method.

In essence, this meant that sites and developers who had been using web standardized code would have to “turn on” standards in IE8 with a specific html META tag. Otherwise IE8 would render exactly like IE7. While this might have helped a few sites maintain backward compatibility, clearly it was not the way to force web developers and users to respect standards and adhere to them.

Case in point: IE’s development team agrees. Internet Explorer 8 will now automatically render sites in “standards mode” without needing to be told to do so. Sites that I built years ago with web standards in mind will finally fully work in Internet Explorer for the first time, this is great news!

I really want to extend my gratitude to Microsoft’s IE team for thinking through this one and listening to the community. It goes to show that things really have taken a change for the better regarding IE. And to be honest, I’m extremely happy that I can give Microsoft a pat on the back for a really trying to do what’s best for their developers and their users.

Good stuff.

When I first heard of Scriptaculous’s new audio playback I was a bit startled. Since when could JavaScript play sound?

For a split second I wondered how I could have missed something so obvious and important in JavaScript and the way it interacts with the Browser and Document object models. Even JQuery seems to have a plugin in development for sound.

When I looked at Scriptaculous’s source I noticed it created sound by adding an Embed tag – a non-standardized tag – which usually points to .wav file, a Microsoft/IBM sound format. This may seem unorthodox to many standards-enthusiasts out there, but I think the author’s decision to add an Embed tag really does underscore a problem with the current state of the Web: standardized sound and audio.

Sound is can be a big component of a truly interactive experience. Visual effects with JavaScript are beginning to match Flash. But without an agreed standard for sound and audio I’m sometimes skeptical as how much closer it can get.

Things don’t seem to be changing any time soon – Ogg Vorbis, the free, open-source audio codec, was removed from HTML5 after opposition from Apple and Nokia.

Since there is no standardized, Free (in the “Libre” software definition) way of adding sound to a Web page, it looks like Web developers will need to use techniques pioneered by Jules Gravinese for Scriptaculous, wait the for next JavaScript audio innovation, or use Flash, which we all know belongs to Adobe.