The default bug view has changed. See this FAQ.

[1.2 branch] parser bugs due to bug 167493

RESOLVED FIXED in mozilla1.2final

Status

()

Core
HTML: Parser
P1
blocker
RESOLVED FIXED
15 years ago
6 years ago

People

(Reporter: dbaron, Assigned: dbaron)

Tracking

({meta})

Other Branch
mozilla1.2final
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

15 years ago
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.
(Assignee)

Updated

15 years ago
Blocks: 182348, 182441, 182498
Severity: normal → blocker
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla1.2final
(Assignee)

Updated

15 years ago
Blocks: 182302
(Assignee)

Updated

15 years ago
Blocks: 182292
(Assignee)

Comment 1

15 years ago
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.

Updated

15 years ago
Blocks: 182442
(Assignee)

Updated

15 years ago
Blocks: 182154
(Assignee)

Updated

15 years ago
Blocks: 182155
(Assignee)

Updated

15 years ago
Blocks: 182315

Comment 2

15 years ago
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.
(Assignee)

Updated

15 years ago
Blocks: 182418
(Assignee)

Updated

15 years ago
Blocks: 181729
(Assignee)

Updated

15 years ago
Blocks: 182449
(Assignee)

Updated

15 years ago
Blocks: 182466
(Assignee)

Updated

15 years ago
Blocks: 182477
(Assignee)

Updated

15 years ago
Blocks: 182482
(Assignee)

Updated

15 years ago
Blocks: 182511
(Assignee)

Updated

15 years ago
Blocks: 182515
(Assignee)

Comment 3

15 years ago
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.
(Assignee)

Updated

15 years ago
Blocks: 182317
(Assignee)

Updated

15 years ago
Blocks: 182268
No longer blocks: 182466
(Assignee)

Updated

15 years ago
Blocks: 182541

Updated

15 years ago
Blocks: 182433

Updated

15 years ago
Blocks: 182253

Comment 4

15 years ago
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 -
(Assignee)

Updated

15 years ago
Blocks: 182282

Updated

15 years ago
Blocks: 182542

Updated

15 years ago
Blocks: 182601

Updated

15 years ago
Blocks: 182608

Updated

15 years ago
Blocks: 182605
(Assignee)

Updated

15 years ago
Blocks: 182626
(Assignee)

Updated

15 years ago
Blocks: 182639
(Assignee)

Updated

15 years ago
No longer blocks: 182542

Updated

15 years ago
Blocks: 182691

Comment 5

15 years ago
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.

Comment 6

15 years ago
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.

Comment 7

15 years ago
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.

Updated

15 years ago
Blocks: 182790

Comment 8

15 years ago
cf bug 182506 comment 7

Updated

15 years ago
Blocks: 182793

Updated

15 years ago
Blocks: 182760

Updated

15 years ago
Blocks: 182802

Updated

15 years ago
Blocks: 182914

Comment 9

15 years ago
Nominating bug 182460 for 1.2.1

Updated

15 years ago
Keywords: meta

Comment 10

15 years ago
Should all depencies by resolved as Fixed since 1.2.1 is out?
(Assignee)

Updated

15 years ago
No longer blocks: 182802
(Assignee)

Comment 11

15 years ago
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
Last Resolved: 15 years ago
Resolution: --- → FIXED

Comment 12

15 years ago
Created attachment 108034 [details]
Also with 1.2.1 bug visible, yet; (offsetWidth-bug avoided)

There is a <div id="SLIDE">&nbsp;</div> on the page INTRO.htm
The a.m. JavaScript works fine for MSIE > 4.01, Navigator4 (special case),
Mozilla > 0.99 but NOT Mozilla 1.2 NOR 1.2.1 !!

Comment 13

15 years ago
Created attachment 108049 [details]
practical example

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

Updated

15 years ago
Blocks: 183179
(Assignee)

Comment 15

15 years ago
*** 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.