The Failures of my First AJAX Application: Part 9

This is the 9th an Final part of my Failures of my First AJAX application series. This is titled: "It accomodated the lowest common denominator in web browsers, therefore it was not as client (as in browser) as I wanted."

Hmm, looking at that I am trying to remember exactly what it meant.

Ahh, now I remember.

I am used to developing in Internet Explorer, so whilst coding and testing the App, I didn't give much notice to Firefox. I kind of just assumed it would work.

The first time I tested in Firefox, I got a lot of security errors (Cross domain data retrieval). Once I had sorted that out by creating proxy scripts I tried it again. This time the errors revolved around the fact that XML DOM model is slightly different in both browsers and requires a little bit more effort in the JavaScript to have the same code that IE and Firefox can both use to process XML nodes.

So basically the moral of the story is that you should always think about cross browser support before you start to develop, it will save you a lot of time in the long run. Think about features that one browser has that the other doesn't. If you do this correctly then you should be able to code around the missing features, much like CSS developers do.

The next version of the application will be completly cross-browser compatible, I might even consider testing it in Safari and the like [I need you, the reader to help me here :)].

That pretty much concludes the Success and Failures series, and it has been a great help to work out the requirements for my next version of the application.

Hopefully one of tomorrows entries will contain the start of formalising some requirements. :)

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.

I'm trialing a newsletter, you can subscribe below (thank you!)