By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,394 Members | 1,912 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,394 IT Pros & Developers. It's quick & easy.

How to get a quicker, more complete answer

drhowarddrfine
Expert 5K+
P: 7,435
I see these mistakes over and over again. Follow them and you can get a quicker and better answer to your questions.

Include a link to your page or the complete HTML and CSS. A picture of the problem does no good without the markup. A verbal description does no good without the markup. Snippets don't always show the whole picture. And use code tags! (The complete HTML and CSS is not necessary if you can supply a link).

Make sure both your HTML and CSS have been validated. Fixing bugs is difficult enough without having to work with errors, too. Validated markup fixes many problems.

Which browser are you talking about? Saying your problem is in IE doesn't tell us if you mean IE6 or IE7. Both work differently from each other. Not indicating any browser at all can be confusing if IE has the problem but we view it in FF.

Tell us what the problem is. Don't give us a link and ask how to fix the problem because the problem may not be obvious to us.

Proofread your post! Sometimes questions asked here contained the most nonsensical gibberish I've ever seen.

Post the generated markup. Supplying us ASP.NET, or Java, or PHP, or Python, etc. code does us no good if we don't use any of those. Same with any other scripting language.

--

Please read the Posting Guidelines
Jan 4 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.