Closed Bug 3880 Opened 26 years ago Closed 24 years ago

[LAYER] JavaScript ticker doesn't work

Categories

(Tech Evangelism Graveyard :: English US, defect, P2)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: roland.mainz, Assigned: bugzilla)

References

()

Details

Seems that the "current" nightly build has various problems with the layout.
Take a look at http://www.planetquake.com with Mozilla 4.x, then do the same
with the nightly build 16.3.1999:
Example problems (not all...):
- the navigation bar on the left side moved into the middle
- the (javascript ??) headline "ticker" does not work
- background is white instead of black
Assignee: troy → vidur
Component: Layout → DOM Level 0
Summary: Various layout problems with complex HTML pages → JavaScript ticker doesn't work
The page is displaying fine with the latest build, and the background color is
black.

There is a problem with the JavaScript ticker doesn't work, so I'm assigning
this to Vidur
Status: NEW → ASSIGNED
A couple of backward compatibility issues:
1) document.layers
2) Image positions (the x and y properties)

Eric, we need to make a final call on compatibility with layers.
Summary: JavaScript ticker doesn't work → [LAYER] JavaScript ticker doesn't work
Target Milestone: M6
Target Milestone: M6 → M9
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 2438 ***
Status: RESOLVED → VERIFIED
VERIFIED dupe. same exact problem at same exact site.
Moving all [LAYER] bugs to Evangelism component for tracking and open-source
evangelism by mozilla community members of sites that need to upgrade to support 
web standards such as HTML 4.0 (instead of LAYER/ILAYER) and the W3C DOM
(instead of Nav4 document.layers[] or IE document.all()). Sites should be
lobbied to do the upgrade using the email templates that are linked to from
http://www.mozilla.org/newlayout/bugathon.html#layerbugs . When a site's owner
has confirmed receipt of the message requesting an upgrade, the bug should be
marked with the keyword evangelized to indicate that evangelism for that bug is
complete. When the site finishes the upgrade and supports standards, the bug
should be closed.
Assignee: vidur → nobody
Status: VERIFIED → NEW
Component: DOM Level 0 → Evangelism
Keywords: evangwanted
QA Contact: petersen → nobody
Target Milestone: M9 → ---
Reclosing as DUP of other report.
Status: NEW → RESOLVED
Closed: 25 years ago24 years ago
SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for 
this component.

Sorry about the spam

zach
QA Contact: nobody → zach
Reassigning Evangelism bugs to me, the component's new owner.  I would like to 
take this opportunity to thank nobody@mozilla.org for all of his dedication, 
contributions, and hard work, and wish him luck at his new job.  Thanks, nobody.
Assignee: nobody → BlakeR1234
Status: RESOLVED → NEW
workaround bugzilla problem that caused a bunch of evangelism bugs to be 
NEW/INVALID, NEW/FIXED, NEW/WORKSFORME or NEW/DUPLICATE
Resolution: DUPLICATE → ---
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: --- → mozilla0.6
Site has been evangelized.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago24 years ago
Keywords: evangwanted
Resolution: --- → FIXED
Verifying bug, as the site now has a new design.
Opening bug 87186 because of problems with new design.
Status: RESOLVED → VERIFIED
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Target Milestone: mozilla0.6 → ---
Version: other → unspecified
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.