Using 12/1 seamonkey build on Win 98 1) Jump to above URL (page has layers, JS, imagemap) 2) content doesn't get drawn 3) compare to 4.x
Also need to process the NOLAYER element correctly.
Status: NEW → ASSIGNED
Summary: This page not drawing LAYER content(probably a DUP bug) → This page not drawing LAYER content
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Old bug, sujay, please check with Viewer and Apprunner. If still a problem, change component to Apprunner. If working, please mark Verified/WorksForMe.
still not drawing the LAYER content on this page..
Summary: This page not drawing LAYER content → [LAYER] This page not drawing LAYER content
Target Milestone: M4 → M6
Assigning all layers bugs to ekrock.
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → WORKSFORME
This one looks like it's either been fixed or that the content of the given url has changed so much that the bug no longer applies. Marking worksforme, with the June 30/99 nightly build on Win '98.
verified in 7/7 build.
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: ekrock → nobody
Status: VERIFIED → NEW
Component: Viewer App → Evangelism
QA Contact: sujay → nobody
Target Milestone: M9 → ---
Closing all Evangelism bugs where no evangelism is needed because page has been fixed, site is internal to Netscape, report is a DUP, or bug report is no longer appropriate for evangelism for any other reason.
Status: NEW → RESOLVED
Last Resolved: 20 years ago → 19 years ago
Resolution: WORKSFORME → INVALID
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 firstname.lastname@example.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: INVALID → ---
marking invalid. w3 has redisigned their site, no longer applies
Status: NEW → RESOLVED
Last Resolved: 19 years ago → 19 years ago
Resolution: --- → INVALID
actually, w3 is Netcsape-internal (behind the firewall). But it's still invalid for that purpose (even though there's already other evangelism bugs on w3 using layers), so vrfy invalid
Status: RESOLVED → VERIFIED
um. /me thinks he is stupid.
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
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.