In article <assdtg$[EMAIL PROTECTED]>, Daniel Wang <[EMAIL PROTECTED]> wrote:
> Henri Sivonen wrote: > > I'm the maintainer of the Mozilla Web Author FAQ > > (http://www.mozilla.org/docs/web-developer/faq.html). TODO is over at > > http://bugzilla.mozilla.org/show_bug.cgi?id=155789 > > I hope to get a new version done in a week. Draft: http://bugzilla.mozilla.org/attachment.cgi?id=108599&action=view > Some ideas > > Introduction > > This document answers questions frequently asked by Web authors and > programmers. The main intent of this document is for general Web page > troubleshooting. Actually, the intent of the document is not to be a general troubleshooting guide but to contain answers to questions Web authors really ask frequently in connection to Mozilla in particular. > 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. :-( > 1 What is Mozilla? > > 1.1 how is Mozilla different from Netscape 4? Is that a real question that is frequently asked by Web authors? > 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? > Mozilla currently has full support Claiming full support is always problematic. There are known bugs, so claming full support will look bad in the opinion of some observers. > 2.1 How do I make sure my Web page works in Mozilla? > > Avoid previewing Web pages in browsers. > > If possible, when authoring a Web page, you should rely on your > knowledge of HTML, CSS, and Javascript only. Previewing in browsers is > bad because 1) browsers have rendering bugs and 2) browsers have > built-in features to recover from errors, both of which are unstable and > undocumented. I agree that Web authoring should be based on knowing the standards and working from there instead of concocting something and seeing how it looks in a browser. I was actually considering approaching the issue from the point of view of the frequent "what the author intended" debates, but I thought the answer would be too hostile. > 2.3 Bug-friendly layout with table > > When doing complex layout, you should use table nesting as much as > possible; try to avoid spanning table cell or even CSS positioning. [...] > In addition, nested tables tend to be structured. Huh? I'm not going to suggest excessive table nesting. > + something on "font-size: 1em" vs "font-size: 1 em" It was there already: | * Lengths other than zero should be followed by a proper unit without | a space between the number and the unit. > + something on size being required Did you mean 'unit'? Suggesting the font size is not required. > 4.2 My DHTML is causing Mozilla to turn scrollbars on and off, what do I do? That question actually shows up from time to time. However, I'm not sure if I want to address it by suggesting workarounds. I usually consider the scrollbar complaints as cases of authors wanting to have too detailed control over the user agent. > - Does Mozilla support downloadable fonts? (remove, answered in 1.3) I've elaborated on the answer based on what I've observed about the motivations of the question. > 5.2 I didn't find the answer I was looking for. Where should I ask? > > comp.infosystems.www.authoring.html Web Authoring FAQ is at > http://www.faqs.org/faqs/www/authoring-faq/ FAQ links added. > need links to real cross-browser tutorials Any suggestions? Thanks for the input. -- Henri Sivonen [EMAIL PROTECTED] http://www.hut.fi/u/hsivonen/
