N
Neal
I'm writing this for all those folks who have an HTML question they want
to post. If someone posts a question in obvious ignorance of the advice,
you might point them to this thread.
****************
IF YOU HAVE A QUESTION, read this whole list first, paying close attention
even to items 10, 11 and 12!!!!
****************
1) Your question might have been covered before. Go to
http://groups.google.com/groups?group=alt.html and search for your topic
first. You might find the answer there.
2) If that doesn't work, use the validator at http://validator.w3.org/ and
be sure your HTML is valid. If you don't understand an error, go back to
#1 and search specifically concerning that question. If Google cannot
help, post on the question here.
3) If the HTML is valid, check CSS for errors too. Try
http://jigsaw.w3.org/css-validator/ . If you don't understand an error,
see above.
4) If that doesn't work, set up a test case on an accessible WWW page.
(Use Geocities, even, if all else fails.) Whittle the code down to the
bare necesseties which still exhibit the problem. (A large page of code is
very hard for us to size up in a hurry, and plus this process often
reveals the error without us having to even look at it. Also, it shows us
that you've put some effort into isolating the problem, which means we'll
be much nicer to you.)
5) If you have searched unsuccesfully, and have valid HTML and CSS (in a
whittled-down version) that still exhibits something unexpected, post the
nature of the problem and the URL to the test case. Do be sure to explain
what your desired effect is, or what you feel is wrong with the rendered
results.
6) Please indicate the browser(s) you've tested the code with, brand and
version, like IE 6 or Opera 7.23. Also, indicate the OS (Windows XP, Mac
OS 9).
7) Remember, this is not a 24/7 help desk. We are here because we like
discussing these matters, not because we want to help you. Therefore, you
may find that there is discussion about the situation, but no answers to
your explicit question. A direct answer should not be expected, nor is any
answer guaranteed. Often a great answer is provided, and if that happens,
hooray for you.
8) If you have not gotten an answer within 4 days, you may request again
in a reply to your original post. (Sometimes we miss something.) If you
get no answers, sorry. If you get unsatisfactory answers, sorry.
9) If you get rude answers, you are entitled to a full refund of all the
money you paid us. Seriously, if you feel a response was overly rude,
sarcastic, or insensitive, please look over your question and be sure you
followed the recommendations I gave.
10) DO NOT multi-post (post numerous posts to separate newsgroups) on the
same topic; if it's really involving PHP and HTML, cross-post to alt.php
and alt.html. Crossposts are only condemned when the post is actually
irrelevent to one or more of the newsgroups involved.
11) Respect our standard procedures. Do not top-post; instead, post your
responses in normal conversation order. Always attribute quotes from posts
and other resources, and always snip unneeded information.
12) I might have missed something. Follow this thread to see what.
to post. If someone posts a question in obvious ignorance of the advice,
you might point them to this thread.
****************
IF YOU HAVE A QUESTION, read this whole list first, paying close attention
even to items 10, 11 and 12!!!!
****************
1) Your question might have been covered before. Go to
http://groups.google.com/groups?group=alt.html and search for your topic
first. You might find the answer there.
2) If that doesn't work, use the validator at http://validator.w3.org/ and
be sure your HTML is valid. If you don't understand an error, go back to
#1 and search specifically concerning that question. If Google cannot
help, post on the question here.
3) If the HTML is valid, check CSS for errors too. Try
http://jigsaw.w3.org/css-validator/ . If you don't understand an error,
see above.
4) If that doesn't work, set up a test case on an accessible WWW page.
(Use Geocities, even, if all else fails.) Whittle the code down to the
bare necesseties which still exhibit the problem. (A large page of code is
very hard for us to size up in a hurry, and plus this process often
reveals the error without us having to even look at it. Also, it shows us
that you've put some effort into isolating the problem, which means we'll
be much nicer to you.)
5) If you have searched unsuccesfully, and have valid HTML and CSS (in a
whittled-down version) that still exhibits something unexpected, post the
nature of the problem and the URL to the test case. Do be sure to explain
what your desired effect is, or what you feel is wrong with the rendered
results.
6) Please indicate the browser(s) you've tested the code with, brand and
version, like IE 6 or Opera 7.23. Also, indicate the OS (Windows XP, Mac
OS 9).
7) Remember, this is not a 24/7 help desk. We are here because we like
discussing these matters, not because we want to help you. Therefore, you
may find that there is discussion about the situation, but no answers to
your explicit question. A direct answer should not be expected, nor is any
answer guaranteed. Often a great answer is provided, and if that happens,
hooray for you.
8) If you have not gotten an answer within 4 days, you may request again
in a reply to your original post. (Sometimes we miss something.) If you
get no answers, sorry. If you get unsatisfactory answers, sorry.
9) If you get rude answers, you are entitled to a full refund of all the
money you paid us. Seriously, if you feel a response was overly rude,
sarcastic, or insensitive, please look over your question and be sure you
followed the recommendations I gave.
10) DO NOT multi-post (post numerous posts to separate newsgroups) on the
same topic; if it's really involving PHP and HTML, cross-post to alt.php
and alt.html. Crossposts are only condemned when the post is actually
irrelevent to one or more of the newsgroups involved.
11) Respect our standard procedures. Do not top-post; instead, post your
responses in normal conversation order. Always attribute quotes from posts
and other resources, and always snip unneeded information.
12) I might have missed something. Follow this thread to see what.