Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

What difference is between web browsers?

Jun 26, 2011 5:23PM PDT

I asking about background differences (how a code line is interpretated, why os IE I get an error and on Firefox it don`t reproduced), not speed differences, on Mozilla Firefox, Google Chrome and Internet Explorer.

Discussion is locked

- Collapse -
Answer
Re: difference between webbrowsers
Jun 26, 2011 5:43PM PDT

Assuming you mean "html and css" when you say "code line", I can only say that both Firefox and Chrome are open source, so just download that to study the details of there engines.

If you us the url and whatever more we need to reproduce the error on IE that isn't an error on Firefox somebody might be able to tell you the cause. But at the moment you don't provide enough info for that.

Kees

- Collapse -
Answer
In addition to what Kees says
Jul 6, 2011 9:00PM PDT

It is well known that, for previous versions of IE at least, Microsoft used their own propriety code for IE and this caused web site developers to include additional lines to their coding to account for the differences. Those new to web page development would not know that of course.

And in fact, since IE9 is now much more W3C compliant than earlier versions of IE, hopefully such additions will soon become a thing of the past.

I hope that helps.

Mark

- Collapse -
why google differ form yahoo or bing ??
Aug 1, 2011 8:46PM PDT

So what you think all things not only browser will be equal Happy
Ahha, get ans from why google differ form yahoo or bing ??

- Collapse -
Cross browsers testing tools
Aug 30, 2011 11:50PM PDT

I tried to find some tools to make some test on different websites. I`m interested to find tools to make the tests more easier. I mean, tools that highlight the compatibility problems, not only to make screenshots of the index.
Do you know any tool or technique to cover this areas?

- Collapse -
Difficult...
Aug 31, 2011 4:27PM PDT

One of the problems is that the testing program would have to know what functionality the webpage has, be able to automatically test it across browsers, and compare the results for differences. That's easy for a math problem, but nearly impossible when considering the wide range of features you can create. Thus, we generally focus more on:
1.) Compatibility charts that let us know what each browser supports/doesn't support properly. Stick to those that work in all browsers you support.
2.) Quality assurance testing where knowledgeable human users (starting with the developers themselves) manually test across browsers.

In the end, there's no substitute for those tried-and-true methods.
John

- Collapse -
Cross browser testing - ways to make work faster
Sep 1, 2011 11:03PM PDT

Thanks John for your answer and your time!

- Collapse -
Indeed...
Sep 2, 2011 3:53PM PDT

Consider testing these forums cross-browser. Most automated services could show you obvious formatting differences by multiple screenshots. However, what about testing what happens when you click 'reply?' Does it appear? Is the area properly formatted? Can you actually type in the text fields? Does the rich text formatter work? Since it is all custom Javascript, there's no out-of-the-box software or service that knows what to do to interact with it and test/compare the results. You can create your own tests on a per-feature basis (unit tests), but most web development ends with a person testing the website manually. The good news: as long as you stick to versions of technologies supported by all of the browsers you want to support (CSS2, Javascript 1.5, et cetera), the variances are kept to a minimum.

John

- Collapse -
What do you think?
Sep 5, 2011 1:19AM PDT

A script that returns code elements used in a website that are not supported by a browser (e.g Mozilla Firefox 6).
By searching on Google "Firefox 6 for developers", on the MDN page are mentioned changes that affect developers. Using that information, I want to write/find a script that returns unsupported elements.