User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008060309 Firefox/3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008060309 Firefox/3.0 See example at: http://home.mnet-online.de/geograf/firefox_bug/logflile.htm (this is a ARS-logfile converted to html for better readability) The name of active Workflow elements is set in bold-tags (<b> </b>) Starting with Line "[6586]" in the example, all Strings beginning with "INC:ICT_" should also marked bold like they all occur before. In MSIE this works without a hitch, in Firefox 3.0 RC1 and all preceding Versions (up from 1.5 tested) not By the way: In MS IE 6.x; 7.x this file is processed MUCH faster (5 - 10 times) on the same PC! Reproducible: Always Steps to Reproduce: 1.Load http://home.mnet-online.de/geograf/firefox_bug/logflile.htm 2.scroll to [6586] in the browser 3.compare view in Firefox with html-code in the file at this point Actual Results: starting with line [6586], all <b> </b> tags in the file are ignored Expected Results: Starting with Line "[6586]" in the example, all Strings beginning with "INC:ICT_" should also marked bold like they all occur before, up the end of the file.

There are a bunch of <ACTL> start tags in this file, but there are no corresponding end tags. This makes the content tree very deep. Gecko protects itself from this by starting to ignore certain tags after the depth reaches 100 or so. This is intentional to avoid hangs/crashes with very deep trees. You can work around it by removing the <ACTL> tags or add a matching </ACTL>.

Thx for quick response - the <ACTL> - bug was fixed in the ARS html-log -generator