This is a meta-bug whose dependencies will be problems caused by the incorrect backout described in bug 167493 comment 21. Some of these bugs have been reported as Windows-only, but I've also been able to reproduce them on a gcc 3.2.1 Linux build with -O2.
I've corrected the backout on the 1.2 branch (although I admit I only tested the change on the trunk, but I did the backout by backing out the backout with cvs up -j<X> -j<Y> and then backing out the original checkin the same way). It remains to be seen what (if anything) we'll do with the 1.2 release.
We may have to do something with the 1.2 branch anyway. Some of the checkins to the 1.2 branch disappeared from the 1.2 release - see bug 182506.
I think I've gone through all the Browser bugs filed between the 1.2 release and now (mostly by just skimming bug summaries), and added all the relevant dependencies. However, bug 182317 and bug 182433 are probably also dependencies of this bug, but I didn't add them since I'm not sure.
Note I've added this bug as a dependency: bug 182253, "document.write() eats initial characters in 1.2" It explains why so many sites with DHTML menus are being hit by the current bug. The sites are using document.write() to create them -
I removed links to 1.2 from the releases page and the home page, and announced the release of 1.2.1 when we have a correct tag and new builds. Since this happened on a 4 day holiday weekend the new release may not happen till Monday.
Hi, Yes I did see it happen in that relase but somebody beated me to the punch. Are you giong to remove it form the ftp://ftp.mozilla.org/pub/mozilla/realses page or you going to keep it there for people to download and test this problem. IF you can e-mail me wiht that info that will be great I will like to see still on there for the people who want to take risks like me.
We're not talking about a security exploit or even major dataloss here. I see no need to re-write history. The 1.2 release will stay where it is. This bug is likely to see some traffic. I'm taking this oportunity to ask all of you folks that read about this bug at mozillazine or slashdot or wherever to not comment. Unless you're actually working on this problem your comments will only get in the way. Thanks.
Nominating bug 182460 for 1.2.1
Should all depencies by resolved as Fixed since 1.2.1 is out?
I have marked all but one of the dependencencies of this bug as fixed, since I tested that they were fixed by the patch that was the change between 1.2 and 1.2.1 when I added them to the dependency tree. (I tested the bugs others added as well.) The one I left out was bug 182433, since the site is unreachable for me. Marking this bug fixed as well, since it is fixed in the release of mozilla 1.2.1.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Completing the previous comment, you may view the site http://www.telstar.int.tf (2nd page) with Mozilla 1.0.1 and 1.2.1
R.N.Gimmel: It's a different bug if you see this with 1.2.1
*** Bug 184236 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.