Solutions to xhtml css web page production problems_HTML/Xhtml_web page production

The solution to the problems in the xhtml css page production process is a bit too much to say that it is a solution. At best, it is just some small suggestions for friends who have just started to learn standard page production. Please forgive me if I am wrong. Of course You can also suggest your better methods so that everyone can learn from each other and grow together!
No matter who you are, you will encounter problems of one kind or another in the process of making pages, and you must solve the problems when they arise. The prerequisite for solving the problem is to know where the problem is. For novices, they may not know where the problem is as soon as they see the problem. For example, in the "extra pig" problem in IE6 (reference: http://www.jb51.net/html-xhtml/webxhtml-6869.html Research on annotations causing text overflow in IE), for some problems it is necessary to Only by sharing and absorbing more experiences can we grow better.
I think everyone has asked questions on the Internet and needed answers from others, but often your questions don’t get answered by anyone, or they are completely ignored. At this time, are you thinking, "Is it because my question is too simple and they don't want to answer it?" "Are they very busy, but they all have time to chat, why don't they help me, do they look down on me?" ?”, or more psychological thoughts. I have encountered this before, and of course it is the same now, but why is this happening? I personally summarized it, and it goes something like this:
1. The way I asked the question was wrong, the information provided was incomplete, and they didn’t know how to help me answer the question
2. For questions of a code nature, I I wanted to keep my code and didn’t want them to see it, so I just took a screenshot and showed it to them
3. They are busy right now. They will look at it later and tell me what the problem is.
4. They Now you are helping me with the test instead of not looking at it for me. When the test results are available, they will tell me naturally (the premise is that the question method is correct, so that others can know what you are asking)
In fact, sometimes there are sometimes problems, just because It's your carelessness that caused it. Therefore, when you encounter a problem, you must first stay calm, then analyze the problem from its roots, and then solve the problem. Below I will briefly share with you some of the ways I usually solve problems, hoping it will be helpful to some friends.
1. Check whether the page has the declaration you need (standard declaration, non-standard declaration, transitional declaration, strict declaration)
2. Check whether the code is written correctly ( Sometimes you may accidentally write the wrong letter, and sometimes you also need to pay attention to capitalization. For example, if you use lowercase in the style, and then use uppercase when calling it on the page)
3. Is the path written correctly? (For some pictures or when styles are called)
4. Use Firebug or IEDevelopertools to check the styles with debugging errors (For these two plug-ins You can search online for its use. I guess there should be a lot, so I won’t talk nonsense)
5. Use the “exclusion method” to solve the problem (This so-called “exclusion method” is just a paragraph Delete the segment structure and keep the problematic segment structure; or directly copy the problematic structure and debug a single problem)
So much nonsense, the main thing is to accumulate more solutions to problems. , try different methods. Generally, you will remember the problem deeply only after you solve it by yourself!