A bit of browsers suitable for web development

27.10.2011 14:11:23 Few talk about browsers, which can be used for web development, do not count those who are tested for cross-browser compatibility.

So the best candidate is the only two FireFox and Google Chrome.
Fire Fox is famous for the fact that there a lot of add-ons and plug-ins. It is Fire bug for debugging HTML, CSS, JavaScript are not interchangeable. It is also an FTP client add all sorts of goodies like JetPack, this add-on allows you to quickly make the additions to Jquery, a couple of scripts you can find in my menu, "Open", and is the analogue of JetPack, this GreaseMonkey I just put it to use had not nothing about it I can not say ... In general, Fire Fox is very tasty for a web developer, but lately he's been terribly ill to work, the latest tuporylye and brake, and Linux systems, it has serious performance problems in Linux, it is completely absent fox multithreading, which leads to hang at the slightest load any script. By the way in Opera there is a similar problem in Linux threads.

The second candidate for the role of the browser for web developer that Chrome had of course there are uncomfortable side, such as search and pasted the address bar, also poorly configured. In Chrome is an analogue of Fire Bug that I Nedao found. Its speed is much greater than Fire Fox and among all the browsers in Linux it mnogopotochen and works steadily. Also, I accidentally discovered that if you use file upload forms Crome shows the percentage of boot files on the server, which is very good.

And in the last paragraph of this article I collision, the two browser with each other in a battle for my preference. In developing its CMS I was using my wrap for lists <select>, my wrapper adds a list of additional functionality lets you filter the contents of a long list. This is often needed when getting a lot of entries and to quickly find a list of filtering. So beloved pup in the past to cope with this task better than anyone else because he understands the style display: none in <option>.
Other browsers refuse to understand this property, they can not just turn off an option list, but do not remove it from sight. Well, okay but not terribly foxes causing problems elsewhere in my Dashed CMS uses ajax to store data, and the page is refreshed fox auto fill port even <input hidden> so we had to put all not a valid attribute specifies not to use the auto fill .
The rest of the Chrome better get on with my CMS, and in the work he was nimble.

Now Ognelis in my heart for second place and is only due to the availability of plug-ins.

Рейтинг $r-- [0] $r++

Показать коментарии (vkontakte.ru)

}