#Chrome Emulator Code Definitely Needs#

4 in the list of most widely used browsers and holds 3.9 share of worldwide usage of web browsers. As reported on 1 December 2009, Chrome was No. Google Chrome derived its name from the вЂchromeвЂ™ of web browsers that is the graphical user interface frame.

Chrome Emulator Code Definitely Needs

As a web developer, you need to agree onВ aВ range of browsers and devices that the code definitely needs to work on with the site owner, but beyond that, you need to code defensively to give other browsers the best chance possible of being able to use your content. You can make some informed calls as to what browsers and devices your users will be using (as we'll discuss in the second article in the series вЂ” see Gotta test 'em all?), but you can't guarantee everything. As long as the site owner is happy with this, then you have done your job.On the other hand, it is not OK for a site to work fine for sighted users, but be completely inaccessible for visually impaired users because their screen reader application can't read any of the information stored on it.Second, when we say 'across an acceptable number of web browsers', we don't mean 100% of the browsers in the world вЂ” this is just about impossible. On modern browsers you might get something animated, 3D and shiny, whereas on older browsers you might just get a flat graphic representing the same information. It is potentially OK for a site to not deliver the exact same experience on all browsers, as long as the core functionality is accessible in some way. To start with, when weВ talk about sites 'working cross browser', we are really saying that they should provide an acceptable user experience across different browsers.

This situation is a lot less bad than it used to be back when IE4 and Netscape 4 were competing to be the dominant browser in the 1990s, browser companies deliberately implemented things differently to each other to try to gain competitive advantage, which made life hell for developers. sometimes browsers have bugs, or implement features differently. Before you even get to cross browser issues, you should have already fixed outВ bugs in your code (see Debugging HTML, Debugging CSS, and What went wrong? Troubleshooting JavaScript from previous topics to refresh your memory if needed).Cross browser issues commonly occur because:

We will look at the different parts of the testing process in much greater detail in subsequent articles, but for now let's just summarize what may occur in each step. If you are working on a large project, you should be testing it regularly, to make sure that new features work for your target audience, and that new additions to the code don't break old features that were previously working.If you leave all the testing to the end of a project, any bugs you uncover will be a lot more expensive and time consuming to fix than if you uncover them and fix them as you go along.The workflow for testing and bug fixes on a project can be broken down into roughly the following four phases (this is only very rough вЂ” different people may do things quite differently to this):Initial planning > Development > Testing/discovery > Fixes/iterationSteps 2вЂ“4 will tend to be repeated as many times as necessary to get all of the implementation done. Workflows for cross browser testingAll of this cross browser testing business may sound time consuming and scary, but it needn't be вЂ” you just need to plan carefully for it, and make sure you do enough testing in the right places to make sure you don't run into unexpected problems. If your site includes a load of big animations, it might be ok on a high spec tablet, but might be sluggish or jerky on a low end device.In later articles, we'll explore common cross browser problems, and look at solutions to those.

From other web sites they own, or from previous versions of the web site you are now working on. Will the target audience for this site be using? The client might already have data about this from previous research they've done, e.g. At this point you'll also want to know how much time you have to develop the site вЂ” what is their deadline, and how much are they going to pay you for your work? We won't go into much detail about this, but cross-browser issues can have a serious effect on such planning.Once you've got an idea of the required featureset, and what technologies you will likely build these features with, you should start exploring the target audience вЂ” what browsers, devices, etc.

You should split the different parts of the development into modules, for example you might split the different site areas up вЂ” home page, product page, shopping cart, payment workflow, etc. You'd have to agree to provide a version of the site without this feature to users of older IE versions.You should compile a list of the potential problem areas.Now on to the development of the site. For example, if the e-commerce site owner wants a WebGL-powered 3D tour of each product built into the product pages, they will need to accept that this just won't work in IE versions before 11. It should also provide an acceptable experience on IE 8 and 9, and be accessible with WCAG AA compliance.Now you know your target testing platforms, you should go back and review the required featureset and what technologies you are goingВ to use. The site should work entirely in the last few versions of the most popular desktop and mobile (iOS, Android, Windows phone) browsers вЂ” this should include Chrome (and Opera as it is based on the same rendering engine as Chrome), Firefox, IE/Edge, and Safari. You can also use a bit of intuition.So for example, you might be building an e-commerce site that serves customers in North America.

Accept that your site just isn't going to work in some older browsers, and move on. Sometimes this is inevitable due to device constraints вЂ” a cinema widescreen isn't going to give the same visual experience as a 4' mobile screen, regardless of how you program your site. Accept that some things aren't going to work the same on all browsers, and provide different (acceptable) solutions in browsers that don't support the full functionality. This may involve writing different code paths that reproduce functionality in different ways aimed at different browsers, or using a Polyfill to mimic any missing support using JavaScript or other technologies, or using a library that allows you to write a single bit of code and then does different things in the background depending on what the browser supports. Get all the functionality working as closely as possible in all target browsers.

Mac Chrome Emulator