New browser version must work with all new processors and Linux versions. The biggest part of the job done by V8 group, who is also working on javascript
engine of the browser. “The v8 team did some amazing work this quarter building
a working 64-bit port. After a handful of changes on the Chromium side, I have
had Chromium Linux building on 64-bit for the last few weeks. I
believe mmoss or tony is going to get a buildbot running, and working
on packaging.” – said Google developer McNamee in this post

The Problem

As is usually the case, Internet Explorer is very forgiving when it comes to
the DOM and lots of times implements alternate methods of accessing certain
functionality.

In my current project I am using the rel attribute to keep track of which row
of data is being accessed. I know some of you may frown on this, however, it is
an acceptable (to me) tactic as this is for a closed intranet where there is no
concern for search engines. In Internet Explorer object.rel is an acceptable
method for accessing the value of the rel attribute of a particular property.

Somehow I worked past this point without testing in Firefox so when an error
kept occurring that was caused by Firefox not liking object.rel it took me a
while to work back through the code to isolate this problem.

The Resolution

The problem has a really simple fix. In my case it was harder locating the
problem then actually fixing it. To get around this problem you don’t need any
object detection, you just need to use the standard method for accessing
attributes, object.getAttribute(’rel’). Go figure.

The Moral Of This Story

The lesson that we should take away from this is to only use approved,
standard methods of functionality. This too will lead you into problems due to
inconsistent implementations but at least you are doing it the right way. You
can then implement your own work-arounds or use a library like Dean Edwards’ IE7
script that will fill in all the holes in Internet Explorer to make it more
standards compliant.