Searched refs:setParsing (Results 1 – 8 of 8) sorted by relevance
220 document()->setParsing(false); // Make the doc think it's done, so it will apply xsl sheets. in doEnd()222 document()->setParsing(true); in doEnd()
1352 …document()->setParsing(false); // Make the document think it's done, so it will apply XSL styleshe… in doEnd()1354 document()->setParsing(true); in doEnd()
635 void setParsing(bool);
1985 setParsing(true); in implicitOpen()2183 void Document::setParsing(bool b) in setParsing() function in WebCore::Document4272 setParsing(false); in finishedParsing()
424 m_frame->document()->setParsing(false); in stopLoading()
16169 Call setParsing(false) explicitly here. It's really annoying that setParsing(true) is done16170 inside DOM::DocumentImpl and setParsing(false) is done by KHTMLPart, so that should be fixed29632 (KHTMLPart::begin): call setParsing on document here after opening29636 (DocumentImpl::open): don't setParsing to true here any more.30687 (DocumentImpl::setParsing):38280 (DocumentImpl::open): call setParsing(true), because we need to know we are once again44533 (DocumentImpl::setParsing):44931 (DocumentImpl::setParsing):
20597 (WebCore::DocumentImpl::finishedParsing): Added. Does a setParsing(false) and then20683 (WebCore::Frame::finishedParsing): Moved code that does setParsing(false) into23076 …(DOM::XSLTProcessorImpl::createDocumentFromSource): Removed the call to setParsing(false) from here
3454 - fixed 3076390 -- crash in DOM::DocumentImpl::setParsing loading thread detail page