- #GOOGLE CHROME VS INTERNET EXPLORER COSTUME HOW TO#
- #GOOGLE CHROME VS INTERNET EXPLORER COSTUME CODE#
Simplistic site issues can be solved relatively quickly and again, we have booleans to isolate IE7-only selectors.Īnd going backwards even further we don’t develop for IE without a special request. On our site for example, I spent nearly 7 hours debugging and fixing small issues and bugs in the methods used to read the site. Luckily, CSS has several booleans that allow us to isolate
![google chrome vs internet explorer costume google chrome vs internet explorer costume](https://images-na.ssl-images-amazon.com/images/I/515Y4dZhnlL._SL160_.jpg)
Again, there are usually a couple of quirks here, but they’re harder to isolate and track down. However, we can get the site to look great in IE9 and even better on IE10 with little to no effort. A couple of quirks such as text-shadow have no chance of working here and while we run polyfills (javascript snippets to make CSS backwards-compatible) some selectors simply don’t work. Internet Explorer is where the fun really comes in. We then check in Safari and, similar to Firefox, the sites very rarely need additional work to work perfectly.
#GOOGLE CHROME VS INTERNET EXPLORER COSTUME HOW TO#
Since we have been building websites for so long, we know how to make it work with very, very little extra work while in development. Firefox runs on a different browser engine and therefore displays sites slightly different. Once we’re done with the development, we begin our cross-browser testing in Firefox. In addition, the newest and most-used versions on Safari run on the same web browser engine (Webkit) and it display websites virtually the same. We can make everything work to the highest degree and level of accuracy and hit the highest number of users in accuracy. We start our developing process in Google Chrome as it has both the highest level of CSS selector acceptance and the highest overall usage in our region. Every website is different, but here’s how we develop most sites to have the most functionality in different browsers and versions. When we build websites, we have to make a judgement call on how in-depth to make a website work in say, IE7, against how it works in Chrome or Mozilla. This means that every versions of every browser reads a website differently.
#GOOGLE CHROME VS INTERNET EXPLORER COSTUME CODE#
The reason is that most browsers use a different “web browser engine” to interpret the code you output.
![google chrome vs internet explorer costume google chrome vs internet explorer costume](http://images6.fanpop.com/image/photos/37000000/15th-Birthday-Internet-Explorer-google-chrome-37036331-600-337.jpg)
![google chrome vs internet explorer costume google chrome vs internet explorer costume](https://d30womf5coomej.cloudfront.net/c/34/bec8dd2f-ccd7-4e2b-86d0-70b5f8407b41.png)
Add into this the fact that every browser looks at code differently and you have quite the pickle on your hands when you’re building websites. If you break down those statistics to a more granular level, in Colorado for example, you would see desktop versions of Safari going down in popularity, mobile browsers edging up and IE levels going down even further in general. The market share for each story complicates the story even further. If you get into mobile browsers the picture gets even more convoluted. There are 10 major versions of Internet explorer, 5 major versions of Firefox, 25+ major versions of Chrome and 5+ versions of Safari.