Common problem solving methods in Xhtml+css Web page production _ Experience Exchange

No matter who, in the process of making the page will encounter such or such problems, out of the question is sure to solve. The premise of solving the problem is to know where the problem is, and for beginners it is not always necessary to see the problem and know where the problem is. For example, in the IE6 "more than a pig" problem, for some problems need more experience exchange and sharing of absorption to better growth.

In the network I think we all have raised questions, need others to answer the time, but often is a problem you do not get anyone to your answer, or is completely ignored. For this time of you, is not think "is because I this question too simple, they do not want to answer" "They are not very busy Ah, but have time to chat ah, why not help me, look down on me?" "Or have more mental thoughts. I've met them before, and of course now, but why? A personal summary of himself, presumably this:

1, I ask the wrong way, the information provided is not complete, they do not know how to help me solve this problem
2, for the code nature of the problem, I want to keep their own code do not want them to see, so only cut a picture for them to see
3, they are currently busy, wait a moment they will read, and then tell me the problem
4, they are now helping me to test, not not to help me see, and so the results of the test will naturally tell me (the premise of the question is the right way to let others know what you are asking)

In fact, sometimes some problems, just because you do not pay attention to lead, so, in the face of problems, we must first stay calm, and then from the root to analyze the problem, then to solve the problem. Below I simply share with you some of my usual ways to solve problems, hoping to help some friends.

1, check whether the page is the declaration of their own needs (standard declaration, non-standard declaration and Transitional Declaration, strict type of declaration)
2, check the code is wrong (sometimes a careless is likely to write a typo, and sometimes the case is also need attention, such as you in the style is lowercase, and then in the page when the call is capitalized)
3, the path is written correctly (for some with the graph, or the style call time)
4, using Firebug or IE Developer tools to check the style of debugging errors (for the use of these two plug-ins can be searched online, there should be a lot of, I will not nonsense)
5, the use of "exclusion" to solve the problem (this so-called "exclusion" is a section of the structure of deletion, to retain a section of the structure of the problem, or directly to the problem of the structure to copy out, a single issue to debug)

Nonsense is so much, mainly or usually accumulate some problems of the solution, try different methods, the problem is generally in their own to solve later, you will remember deeply!