Which browser should we use to render HTML CSS when creating a site and why?

  • Firefox Latest Version
  • IE7
  • IE6
  • IE 8

Which browser should we use to render HTML code always and why?

Edit:

My question is not on which browsers I should check the site before going live. I will try to check everything possible.

My question is: which browser should I choose during the layout development process and why?

because during development it is impossible to see every step in the entire browser, it will waste time. after creating the layout, we can test everything, but during development one browser will be better.

+4
source share
11 answers

Wow ... each one?

I personally develop Firefox 3.6 for the convenience and accessibility of Firebug, header covers, and other tools. I am trying to test in all browsers that you mentioned before something comes out so that someone sees (e.g. client). But I don’t think that there is a real “best” choice, because, in the end, you will need to test all the browsers that you need to support anyway.

+5
source

Use the latest CSS compatible browser with a good debugging tool, for example. Firefox 3.6 and the Firebug plugin.

Then check out the other browsers that you want to support for your users and return the bug fixes.

Do not try to make the site look EXACTLY the same in all browsers, you will be wasting your time.

While the effect is similar in old / other browsers (for example, you can use the border radius for Firefox / WebKit browsers, and this will deteriorate well for browsers that do not support the border radius), and the site can be used and fulfill its purpose, then your ok

DO NOT ALLOW TIME TUNES IN IE6. Use a conditional numbered style sheet and just use it ...

In the title of the document

<!--[if IE 6]> <link rel="stylesheet" type="text/css" href="IE6.css"/> <![endif]--> 
+2
source

It all depends on your target user group.

If you are working with a client that uses IE6, you will have to test it. Sadly, I know.

If you are developing a site for the general public, then check the current versions of major browsers. Firefox, IE, Opera, Safari and Chrome (?).

Also: develop in accordance with the standards, then fix everything that does not work in one browser. Not what you are developing for IE, and then trying to fix everything that suddenly breaks down on all other browsers.

+1
source

During the development of NOT testing, I use this combo:
firefox
firebug extension
webdeveloper extension
HTTP header extension
Try it, you won’t regret it, you can make changes to your css IN BROWSER, and then change your code (no longer needs updating for this annoying one-pixel offset), check where the interface or error code is located, logic, and much more. (Page Speed ​​and YSlow to analyze your page speed, etc.)

+1
source

You need to test your css in all major browsers, including IE (6, 7 and 8), Firefox, Chrome and even Safari and Opera.

You may be able to simply use the latest versions of Firefox, Chrome, etc., since they automatically update, and therefore users are less likely to use the older version (although it is not unknown).

IE is a problem because many users, especially corporate users, work with older versions.

Choose one, it doesn’t really matter to what extent it has good development tool support in order to develop and get a site that is good. Then check in others. What order you do and how much effort you want to spend depends entirely on your target audience. In my experience, Firefox with Firebug and even (I dare say) IE8 with its built-in developer tools is a good choice. The advantage here is that you reach most users with these. However, as the browser market becomes more fragmented, you will need to test others.

0
source

I totally agree with Pekka.

I develop everything in Firefox and use the excellent add-ons available during development (Firebug / Web Developer Toolbar / etc).

It was also supposed to be tested frequently in other browsers ... I would recommend that every time you go for a little rest, check it in other browsers to see if there are any problems, and then make a note to fix them and allow your web -site is displayed correctly in all browsers.

You really do not want to exclude any user based on his / her browser preferences, so make sure that he works in all directions!

change

Also, one of the other users has a good moment ... IE6 is in the process of gradual failure, however, if you want users to have any users in the corporate environment, you also do not want to exclude testing!

0
source

This is an interesting question, I'm going to assume that you have a process that means that you first design your page and then do cross-browser testing to make sure that it works everywhere - this begs the question which one I'm going to deliver to you the best starting point for working “everywhere” (the definition of which will depend to some extent on your target audience).

It was easy - in my (then) Firefox staff they had good standard support and the best tools - so do it right in firefox first and then adapt to handle everything else, now it's much less clear, since IE8 has a very decent set developer tools (and behaves better than its predecessors), and Chrome is now taking effect - again with a good set of tools and extensions.

My gut feeling is probably Firefox, Chrome, IE8 in that order - but I am not doing anything suitable for CSS to claim it to be correct.

0
source

You are developing in Firefox (you have firebug to configure things), you are testing safari / chrome and opera (they are all fine with the standards, so you have a small chance of errors) and you are debugging in IE. Since from one attempt it is impossible to fully function in the entire browser: D

0
source

I use my main browser (Chrome) to make major progress and often check all other browsers for errors and layouts.

0
source

I think that if we choose firefox and IE 6.0 as the website design, the site will look almost the same for all browsers, because the rest of the HTML rendering of all IE 6 and 7 browsers is almost the same. So, if we make css from the very beginning by looking at firefox and IE 6.0, there will be fewer errors, and so we can make all browser-compatible websites.

Please give me feedback

-1
source

I do this in ie6, the most primitive browser that is still in use. I think that any thing that will work on ie6 will work in any browser.

-2
source

Source: https://habr.com/ru/post/1302469/


All Articles