What is the best internet browser for Web designing?
Posted on February 6th, 2010 by admin
What is the best internet browser for Web designing? And what is a feature that helps with web designing?
I’M using Windows Vista.
For initial development, my shop uses Firefox. Not only is FF among the most compliant with W3C standards, but with the (feature!) Firebug plug-in, it makes development MUCH faster. The majority of what works, e.g., HTML, CSS, and JavaScript, in FF works as-is for Chrome, Safari, Opera, etc i.e., the non-IE, graphical browsers. Once everything is beeyoo-tee-full in FF, we move to making it work for IE 6, 7, and 8 on XP, Vista, and 7…yes the same version of IE works differently stupidly on various versions of (expletive deleted) Windows. However, using conditional comment, the odd bits to cure IE silliness can be accomplished. For instance, we usually end up with several CSS files by following the model:
- file1.css: get it perfect in FF and the other non-IE browsers
- file2.css: minimum differences to fix IE8 and anything older that works the same
- file3.css: minimum differences to fix IE7 and anything older that works the same
- file4.css: minimum differences to fix IE6
Since IE5 is used by less than .5% of users these days, we ignore it. As browsers drop off the user radar, we’ll quit supporting them as well. Currently, tho’ I hate the fact, IE is used by WAY big bunches of people. Since, my shop has to make our clients look good (even to the poor, benighted folks who use Windoze and IE and the artsy, Mac-sy Safari types), we support lots of browsers.
Same arguments hold for scripting, but we usually perform minimal browser "sniffing" in the context of the script code.
February 6th, 2010 at 8:52 pm
It depends on your target platform.
Mac, Win or Mobile?
References :
February 6th, 2010 at 9:19 pm
For web designing, all browser are equally important since different people using your site will access it through different browsers.
Now firefox probably has extensions and all (what does firefox not have?), but I like chrome (by google), especially because of a certain thing called "inspect element."
On any web page, right click, and then click the inspect element button — that is one of the greatest resources a web developer could have (because it gives you information about a particular element on a page, and highlights that element and shows you what’s going on with that piece over there).
There are plenty other uses of the inspect element option. But yes, for testing purposes, you must test across all the browsers.
Good luck!
References :
February 6th, 2010 at 9:52 pm
google chorme is really fast and also it has cool themes
References :
February 6th, 2010 at 10:28 pm
For initial development, my shop uses Firefox. Not only is FF among the most compliant with W3C standards, but with the (feature!) Firebug plug-in, it makes development MUCH faster. The majority of what works, e.g., HTML, CSS, and JavaScript, in FF works as-is for Chrome, Safari, Opera, etc i.e., the non-IE, graphical browsers. Once everything is beeyoo-tee-full in FF, we move to making it work for IE 6, 7, and 8 on XP, Vista, and 7…yes the same version of IE works differently stupidly on various versions of (expletive deleted) Windows. However, using conditional comment, the odd bits to cure IE silliness can be accomplished. For instance, we usually end up with several CSS files by following the model:
- file1.css: get it perfect in FF and the other non-IE browsers
- file2.css: minimum differences to fix IE8 and anything older that works the same
- file3.css: minimum differences to fix IE7 and anything older that works the same
- file4.css: minimum differences to fix IE6
Since IE5 is used by less than .5% of users these days, we ignore it. As browsers drop off the user radar, we’ll quit supporting them as well. Currently, tho’ I hate the fact, IE is used by WAY big bunches of people. Since, my shop has to make our clients look good (even to the poor, benighted folks who use Windoze and IE and the artsy, Mac-sy Safari types), we support lots of browsers.
Same arguments hold for scripting, but we usually perform minimal browser "sniffing" in the context of the script code.
References :