25362 - syracuse.com - [LAYER] Entire web site doesn't render well

Status: RESOLVED FIXED

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

Description

[Scott Springer]

Summary is pretty self explanatory!  Links won't work, pieces don't show up in
the right places, etc.

For example, there is a menu (probably javascript) at the left of the page.  The
menu items don't show up there like they are supposed to, but they render at the
bottom of the page.  Hard to describe - easy to understand when you see it.

Also, you place your mouse pointer over a link and the icon doesn't change.  You
click on it and you don't go anywhere.  It doesn't seem to want to recognize the
links on the page.

Front page might work.  Surf around on site and see what happens.

Comment 1

[Sean Richardson]

Confirmed with 2000-01-31-08-M14 on Windows NT 4.0.

This page does have serious problems with its javascript-driven menus.

Anybody want to try reducing this to a testcase before this gets passed to
one of the "DOM" components. There is no document.layers here but I can't vouch
for the js otherwise.

Links above the sidebar menu that it messing up do work, the rest don't,
whatever "column" they may be in, so that problem is probably secondary to the 
js problem.

Comment 2

[leger]

Assigning all open "[e-mail]" bugs to "[e-mail]" to weed 
thru.

Comment 3

[Doron Rosenberg (IBM)]

This is a css bug (Absolute Positioning)

The line:
<DIV ID="NAVSPAN" STYLE="position: absolute; top: 195; left: 10">

causes all links on the right-hand side not to work as long as the left-hand
menu table is created (when it ends, links below it work).

Taking out "position: absolute" makes all the links work

Comment 4

[Sean Richardson]

Updating QA contact to match component. Not sure which of the 17 other 
"absolute pos" bugs this is going to be a DUP of...

Comment 5

[Richard Zach]

Reassign to component owner.

Comment 6

[Marc Attinasi]

The part about the links not working in an absolutely positioned DIV is a dup of 
bug 24474 which both looks very similar and acts the same. 

The JS menu bugs are another story altogether.

Comment 7

[Marc Attinasi]

Taking over 1/3 of Pierre's NEW bugs to help reduce his doomage factor

Comment 8

[Pierre Saslawsky]

Reassigned back to me these bugs that shouldn't have left my list.

Comment 9

[Pierre Saslawsky]

JS menus don't work because they rely on layers (which are no longer supported).
Reassigned to ekrock to evangelize the webmaster.

Comment 10

[ekrock's old account (dead)]

INVALID. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav6. 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!

Comment 11

[Christine Hoffman]

Verified invalid

Comment 12

[ekrock's old account (dead)]

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.

Comment 13

[ekrock's old account (dead)]

Marking bug evangelized and clearing cc:s as courtesy to reduce spam.

Comment 14

[Zach Lipton [:zach]]

SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for 
this component.

Sorry about the spam

zach

Comment 15

[Blake Ross]

Reassigning Evangelism bugs to me, the component's new owner.  I would like to 
take this opportunity to thank [e-mail] for all of his dedication, 
contributions, and hard work, and wish him luck at his new job.  Thanks, nobody.

Comment 16

[Zach Lipton [:zach]]

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.

Comment 17

[Zach Lipton [:zach]]

Sorry about this problem. I somehow screwed up the keyword changes. 
Sorry about this spam.

Comment 18

[Blake Ross]

-> [e-mail] for my evangelism bugs.

removing the now-depreciated evangelism-related keywords.

setting platform to All.

Comment 19

[Blake Ross]

Reassigning evangelism bugs to [e-mail].

Comment 20

[Zach Lipton [:zach]]

evangelized site using layer letter tool.

Zach

Comment 21

[Bob Clary [:bc] (inactive)]

All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.

Comment 22

[Zach Lipton [:zach]]

site has been fixed in bits from 11/10. RESOLVED FIXED

Comment 23

[Bob Clary [:bc] (inactive)]

sorry, not fixed.
Error: document.NAVSPAN has no properties
Source File: http://www.syracuse.com/dhtml/hnavbar/scripts/hGlobal.js
Line: 9

Error: top_coord is not defined
Source File: http://www.syracuse.com/dhtml/hnavbar/scripts/hData.js
Line: 1

Error: hNAVBAR has no properties
Source File: http://www.syracuse.com/
Line: 398

Comment 24

[Doron Rosenberg (IBM)]

-> moi

Comment 25

[Doron Rosenberg (IBM)]

http://www.nexgenmedia.net/evang/syracuse.com/www.syracuse.com.html is the fixed
version (only menus)

contaced via webform

Comment 26

[Doron Rosenberg (IBM)]

positive responce. he even asked me to look into his personal site's dhtml :)

Comment 27

[Michael Gabriel]

looks like the site got a mayor js free redesign to me ... WFM

Comment 28

[Doron Rosenberg (IBM)]

menus still broke

Comment 29

[Bob Clary [:bc] (inactive)]

tech evang june 2003 reorg

Comment 30

[Travis Chase]

maybe its just me but I can't find any broken menu's on syracuse.com,

and a side note, Syracuse needs better recruiting, there College football team
stinks, maybe a standards compliant website will help that out.

Comment 31

[Bob Clary [:bc] (inactive)]

Warning: The stylesheet http://www.syracuse.com/css/home.css was loaded as CSS
even though its MIME type, "text/plain", is not "text/css".

Warning: The stylesheet http://www.syracuse.com/css/hp.css was loaded as CSS
even though its MIME type, "text/plain", is not "text/css".

Error: SuperBannerFlash is not defined
Source File: http://www.syracuse.com/
Line: 57

Error: document.NAVSPAN has no properties
Source File: http://www.syracuse.com/dhtml/hnavbar_class/scripts/hGlobal.js
Line: 9

Error: top_coord is not defined
Source File: http://www.syracuse.com/dhtml/hnavbar_class/scripts/hData.js
Line: 2

Error: hNAVBAR has no properties
Source File: http://www.syracuse.com/
Line: 448


Considering I am in Central VA, no wonder the Hokies beat the crap out of them. :-)

Comment 32

[Travis Chase]

Whoops my bad, i forgot to look at the Java Script console, I was looking for
tactile errors and such :) I didn't scratch the surface.

Virgina Tech deserves to keep there #4 ranking

Comment 33

[Travis Chase]

I just found the drop down recipeint selector for the Syracuse.com feedback, fourm
will not drop down. under Mozilla or Firebird

Comment 34

[Travis Chase]

Correction I meant to type Will drop down in Mozilla but not firebird

Comment 35

[Ian Schorr]

Site has changed considerably, do any of these bugs still exist?  If not, should
be bug be closed?

Comment 36

[Pascal Chevrel:pascalc (PTO until April 26)]

drop down menuw still not working

Comment 37

[Chris Lawson (gone)]

I don't see any drop-down menus at all any more. I'm going to resolve this FIXED. If there are any more problems, please file new bugs for them.