Thanks.. ;-) I think I've found part of my answer in nsHTMLDocument::StartDocumentLoad (http://mxr.mozilla.org/mozilla- central/source/content/html/document/src/nsHTMLDocument.cpp#1129)
1129 mParser->Parse(uri, nsnull, (void *)this); But the document reads that *necko* is really the one who triggers the parsing process... but from the line above, it seems to me it's triggered by being called by an nsHTMLDocument object... I don't understand how is necko involved in parsing..? And it seems to me that nsParser::Parse(...) the function is defined just to initialize some member variables : http://mxr.mozilla.org/mozilla-central/source/parser/htmlparser/src/nsParser.cpp#1296 . I don't understand how does this call trigger the parsing procedure? I must have missed something... thanks! Kenny. On May 27, 10:21 am, byang <[EMAIL PROTECTED]> wrote: > On May 27, 12:46 am, Kenny YU <[EMAIL PROTECTED]> wrote: > > > i have a question here... > > > In AppShell, the execution calls LoadURI which then lead into > > DocShell.... and in CreateContentViewer method of docshell, a content > > viewer (document viewer) is created. and Presshell and frames will > > then be associcated to this document viewer (as I understand). > > > I suppose after an ContentViewer instance is created, HTML parsing > > process should follow... but what triggers the parsing to start? any > > listeners involved are triggered, for example...? > > As far as I know, the loading phrase is a really very complex phrase. > The real network load start in the > uriload/nsURILoader.cpp file: > > in the OpenURI mehthod. > rv = channel->AsyncOpen(loader, nsnull); > > And this method is called from the nsDocShell loading method. > > Good luck in hacking. > > Regards! > Bo _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
