LaesyT wrote:Hi.
I'd like to know if are there any differences in renderings between Trident, WebKit and/or FireFox?
Thanks for asking LaesyT.
This is a VERY good question.
eValid, as you make know, relies on the IE browser for processing and rendering websites. That means that eValid uses the Trident Rendering Engine, which is also referred to as IHTMLDocument2+ in C++.
Other browsers do NOT use the Microsoft browser, but have there own rendering engines. There are many possible rendering engines, and there are lots of versions of them.
Chrome, for example, uses a variant of the Apple-developed WebKit rendering engine, whereas FireFox has its own variation of that.
But the REAL question is whether the differences are significant?
If you take an extreme view, yes, there are differences. But if you take the practical view, the differences are small and don't generally affect how a web application behaves.
But there are exceptions: we have seen applications that insist on using a particular browser, e.g. FireFox, and refuse to work with IE or Chrome or Safari. This is easy to do at the server level: you simply not the UserAgentString and deny access to those browser which you don't want to support.
And yet, an application that is going to be of practical commercial use can't really try this kind of trick. Which is why the vast majority of applications use the commonly supported funtions that are available consistently in all of the different browsers. It makes practical AND commercial sense.
-- eValid Support
by LaesyT » Thu May 15, 2014 1:25 pm