181729 - Does not shown

Status: RESOLVED FIXED

(SeaMonkey :: General, defect)

Description

[Eugene Savitsky]

The code is not shown in mozilla. 

Shows in Opera, Ie.

moz 20021121

Comment 1

[Thomas Holaday]

I get a yellow banner ad for Sky Radio.  Looks the same in Opera.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021122

Comment 2

[Andrei Leo]

This occurs for 1.2 brunch build only

Confirming with
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021121

Comment 3

[Boris Zbarsky [:bzbarsky]]

Eugene, are you using a trunk or branch build?

Comment 4

[Eugene Savitsky]

Branch...

Comment 5

[Boris Zbarsky [:bzbarsky]]

Then please mark that in the version field.  Worksforme on trunk too, so.

Comment 6

[Eugene Savitsky]

Why did you closed that if this does not work?

Comment 7

[Boris Zbarsky [:bzbarsky]]

It works on the trunk.  It will not be getting fixed on the 1.2 branch because
that branch is not taking any fixes except major crash problems and the like. 
So it's worksforme.

Comment 8

[Eugene Savitsky]

And if that would affect many sites? There's a very simple code...

Comment 9

[Boris Zbarsky [:bzbarsky]]

If you can point to the bug that fixed this on the trunk, feel free to nominate
that fix for the branch.  But even fixes for more serious problems than this are
not being taken on the branch at this point....

Comment 10

[Bill Mason]

*** Bug 182440 has been marked as a duplicate of this bug. ***

Comment 11

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This is 1.2-branch only because of bug 182500.

Comment 12

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Reopening, since this was a valid branch bug.

Comment 13

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I have tested that this bug was an instance of bug 182500 / bug 182253 based on
comparison of two Linux builds compiled with gcc 3.2.  This bug was present in
the 1.2 release and was the only bug fixed in the 1.2.1 release (and the reason
for the 1.2.1 release).

Marking this bug as fixed since it should be fixed in the 1.2.1 release.