IE dominance challenged Cross browser test knowledge

IE dominates the world in those days, the Web designer occasionally fell into ie with its competitors, however, when some new, Web-oriented browser appeared, things changed, IE's dominance was challenged.

An important part of WEB design and developer work is cross-browser testing, who let us live in this happy and painful era, there are so many browsers in front of us, there is the nightmare of the total can not get rid of IE6. This article describes a variety of issues and knowledge related to Cross-browser testing, including rendering, platforms, devices, and JavaScript engines.

Dream Five Combination

IE dominates the world in those days, the Web designer occasionally fell into ie with its competitors, however, when some new, Web-oriented browser appeared, things changed, IE's dominance was challenged. As things have changed, the advent of mobile browsers and new rendering engines has allowed WEB designers to begin to consider problems with cross-browser testing. Today, WEB designers are increasingly targeting 5 or 6 major browsers, but things don't end, and it's always a dream forever.

While the browser market is dominated by 5 big browsers, it cannot ignore the other 0.87%.

In general, cross-browser testing is for different rendering engines, and if you've already tested a mainstream rendering engine such as Trident,gecko,webkit,presto, it seems to be safe to say. However, testing for a wider range of devices and platforms is still necessary to help you uncover a number of potential problems.

Trident (Internet Explorer), Gecko (Firefox), Webkit (Chrome and Safari) and Presto (Opera).

Basic test

At present, a serious problem is device dependencies. Apple has been hell-bent on refusing to support Flash,apple and Adobe against each other in the IPhone and IPad. Although Flash itself is responsible for content rendering, it is imperative to expand your testing scope by simply testing in mainstream browsers and still not finding potential problems.

Flash renders its own content, but not all browsers support Flash.

Another issue is the version of the render engine, which is important to support the latest version, while many devices are still using the old version of the rendering engine, which requires that we test both the old and the new versions of the render engine.

Internet Explorer 6.0 uses a BUG-ridden old Trident render engine the problem of rendering engines

is not only between versions, but also different platforms and devices, and there is no doubt that for a variety of platforms , tests of all kinds of equipment will make you mad. Designing for small screens is not easy, especially when there is no agreement between the different devices. This exists in the middle of the desktop system, with the same rendering engine, and on different platforms, there is still a slight difference.

A List Apart The rendering differences, they simply designed a separate version for mobile devices

In addition to rendering differences, cross-browser compatibility has a more important problem with javaScript engines. In the early days, the only problem with JavaScript was whether it was enabled, but now, the different browsers with the same rendering engine often have a large and varied JavaScript engine. You need to test JavaScript performance against different browsers, especially if you're using a lot of JQuery's gorgeous effects.

This is the Chrome test site to show the performance of Chrome JavaScript.

Finally, is an accessibility issue. You have to understand that when someone with some sort of obstacle visits your site, accessibility issues force them to use only a certain browser, and in that case, remember that you can't ignore these people who are often forgotten.

Opera, although only a small market share, has a voice function that means all

for people with special needs

Long-term perspective

Accessibility issues, different JavaScript engines, cross-platform issues, rendering differences, technology dependencies, and so on will make you sigh commiseration, but that's not enough and you need to study your target audience. Take the time to communicate with your visitors and end their needs, for example, by using polls to figure out the browser distribution your visitors use, and eventually you will find that you may also be designing for mobile browsing, or for the iPhone.

A similar statistic allows you to understand the browser distribution of your site visitors

Rendering engine for different platforms

Here's a list of browser rendering engines for mobile and desktop platforms, and we'll see more and more browsers coming out, so consider for the future.

A considerable number of rendering engines are available under the desktop and mobile platforms

The following browsers use the Trident engine

The following browsers use the Gecko engine

The following browsers use the Webkit engine

Browsers using the Presto engine are mostly limited to Opera

Summarize

Maybe your site doesn't have any errors, and it may look great on every occasion, but for true cross-platform compatibility, 5 Big browser tests are still not enough. If this article teaches you only one thing, it is to take the time to communicate with your visitors and analyze their needs. In addition, take time to test various platforms, each rendering engine for various devices, and perform performance testing for different JavaScript engines. In a Web-led world, it is worthwhile to take the time to extend your site to as many people as possible.