I’ve been using jQuery since at least mid 2008 and have to say that I just love how much easier things are and not having to generally deal with the cross-browser issues in Internet Explorer, Safari,Chrome, and Firefox.
In the roughly two years that I have worked with jQuery, I have referred to a couple of things to learn jQuery and improve my web based applications.
Rebecca Murphy wrote an excellent electronic book called jQuery Fundamentals that she gives away for free from her website. jQuery itself also has many video tutorials, and a fairly well written and maintained web based manual that works similar to a Wiki.
Hope this helps!
Conveniently, Firefox Throttle meets my needs exactly and allows exclusions for specific websites or specific IP Addresses.
I am having problems getting mozilla firefox to display my website correctly. It works fine on Internet Explorer. So I was thinking of making a mirror of the website that is made specifically for firefox browsers. Is it possible to code a website so that it detects what browser a visitor is using and them sends them to the correct mirror ?(i.e. index_firefox.html or index_ie.html)
At the root of this question, there lies a huge problem that really never would have occured if browser creators followed the w3c recommendations. Microsoft and Netscape fought the original browser wars in the 1990s and throughout this time both created proprietary nonstandard tags and didn’t always follow the w3c recommendations. Eventually, Microsoft’s Internet Explorer won the war and Netscape disappeared into the oblivion to eventually become the Mozilla Project.
Mozilla Firefox, Opera, Safari and Chrome basically render almost exactly (99% of the time) the current w3c recommendations for css,html, and javscript and most of the draft recommendations are followed in the current builds of these browsers. Internet Explorer on the other hand, barely follows any of the w3c recommendations from even the year 2000. IE’s terrible rendering results in us having to perform significant testing and spend significant amounts of time doing IE6, IE7, and probably now IE8 hacks.
Problems With Potential Solution
I believe that redirecting based on a browser is a terrible idea, and should be avoided at all costs because of the potential doubling or trippling of work with regards to content.
Avoid the use of redirections for different browsers and instead developing a website that is 100% standards compliant and than start to add IE hacks as necessary.
How do you test browsers? I don’t usually try for perfect pixel positioning in every browser, but if the client asks I won’t complain!