Some questions about cross-browser testing

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 problem 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 us to test both the old and the new versions of the rendering engine.

Internet Explorer 6.0 uses a BUG-ridden old Trident rendering engine

The problem with the rendering engine is not only between versions, but also with different platforms and devices, and there is no doubt that testing a variety of devices for a variety of platforms will drive you crazy. 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.