This is a plea to Apple…
to update Safari to the latest webkit. The fact that it fixes a whole lot of javascript bugs is alone a strong enough reason to do so, for me at least :).
bla.onclick = function(){
document.getElementById(’selected’).id = ‘none’;
this.parentNode.id = ’selected’;
}
All browsers except Safari require developers to reset the previously selected tab before applying the selected class to the current one. Safari wants it the other way around or else it will return null when document.getElementById() is fired. Latest webkit fixes this problem.
Update: Never mind, it was my code that was making the havoc. But I still stand by my plea though. Here’s another one that I found while working on the same map project. Apparently long is a reserved keyword in the current Safari’s JS engine. It’s not in the latest webkit.
But it’s probably not a well-known bug (some might call it a feature) unless you’re working on some kind of geo-data project where long normally refers to longitude.
