Closed Bug 5228 Opened 26 years ago Closed 24 years ago

[LAYER] Image are not lineup properly

Categories

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

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: zaw, Assigned: bugzilla)

References

()

Details

Well.. I work there, i didn't create the page. But I beta tested and Just some minor Layout porblem not as bad as zdnet one.. Image on differnt layers does not lineup properly.. I believe person who created the webpage are same peoples who created ZdNet's page.
Oh yeah.. I was using M4.
Assignee: troy → vidur
Another LAYER related problem
Status: NEW → ASSIGNED
Summary: Image are not lineup properly → [LAYER] Image are not lineup properly
Target Milestone: M9
The site will be change to http://www.quantum.com after may.
Assignee: vidur → ekrock
Status: ASSIGNED → NEW
Assigning all layers bugs to ekrock.
Blocks: 8023
Status: NEW → ASSIGNED
Target Milestone: M9 → M15
Setting all LAYER bugs to M15 for as-time-allows evangelism.
Visited The website again with 7-23-11 Nekko Nightly Build and imges seem to line up 'OK, except for Speacer (GO) (S) (H) (P)
But Not on The 1999070308 M9 Build.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
INVALID. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav5. Closed. Notified reporter and site owner via template at http://sites.netscape.net/ekrock/fixit/layer.html In the future, if possible, please INVALID, notify, and close such bugs directly using that template without assigning to me. Thanks!
Status: RESOLVED → VERIFIED
Marking verified invalid per last comments.
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: Layout → Evangelism
Keywords: evangwanted
QA Contact: petersen → nobody
Target Milestone: M15 → ---
Marking bug evangelized and clearing cc:s as courtesy to reduce spam.
Keywords: evangelized
Resolution: 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 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
Removing the evangwanted keyword from 49 evangilizm bugs that also have the evangelized keyword. Having both of these keywords on a bug makes it really hard to do a query for all open evangilizm bugs that are evangwanted. Sorry for the spam.
Keywords: evangelized
Sorry about this problem. I somehow screwed up the keyword changes. Sorry about this spam.
Keywords: evangwantedevangelized
Severity: normal → major
Status: NEW → ASSIGNED
OS: other → All
Priority: P3 → P2
Hardware: PC → All
Target Milestone: --- → mozilla0.6
Site has been evangelized.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago24 years ago
Keywords: evangelized
Resolution: --- → FIXED
Looks the same or better than Netscape 4.x Verifying.
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.