I attached a new draft to the bug: http://bugzilla.mozilla.org/attachment.cgi?id=110719&action=view
In particular, I'd be interested in comments on the answer to the answer http://bugzilla.mozilla.org/attachment.cgi?id=110719&action=view#intentio ns In article <astv56$[EMAIL PROTECTED]>, Daniel Wang <[EMAIL PROTECTED]> wrote: > Anyhow, the document should explain its intent and the intended audience. I added a short explanation about the intent of the document. > >> Reading this FAQ requires basic understanding of HTML and CSS. > > > > That is implied in the document title. Sadly, there are Web authors who > > lack the basic understanding of HTML and CSS. :-( > > Web monsters who ask "how do I do" or "why is it broken" type of > questions are generally the clueless ones (unfortunately). Those who > knows what they are doing are capable of solving their own problems and > usually only visit public forums to help others :( Not necessarily. Asking the questions is a lot more clued reaction than jumping to the conclusion that the browser is broken or something like that. People usually can't solve all their problems themselves. Getting help doesn't imply cluelessness. Besides, doctype sniffing can be really confusing even to smart people who just haven't read about it, yet. > So unfortunately we need say it aloud that good coding requires good > knowledge of HTML/CSS/JS... Starting with "in order to read this document intented for Web authors, you need to know the basics of HTML and CSS" could put off some author who think that is an obvious requirement. > >> 1.3 What standards are supported by Mozilla? > > > > I think that question is typically asked by people who want to engage in > > Mozilla advocacy or want to write about Mozilla. Is it really a frequent > > question from Web authors? > > No. Web monsters don't care about standard support, but it doesn't hurt > to point out importance of standards. Putting infrequently asked questions that you *wish* were frequently asked in a FAQ made it to Jakob Nielsen's "Top Ten Web-Design Mistakes of 2002". > We also need something on <link> element support. I haven't noticed frequent questions about it. -- Henri Sivonen [EMAIL PROTECTED] http://www.hut.fi/u/hsivonen/
