Closed Bug 182433 Opened 22 years ago Closed 22 years ago

Problems with DHTML and JScript

Categories

(Core :: DOM: HTML Parser, defect)

Other Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: hs, Assigned: harishd)

References

()

Details

(Whiteboard: [Bug only in 1.2 builds; site works with trunk builds])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021127
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021127

We have tested this site site Mozilla 1.0 respectively Mozilla 1.1 and Internet
Explorer > 5.0.
On the left hand side you can see a DHTML menu which does not seem to be
displayed in 1.2. The links seem to work.
Also: A button on the upper edge of the site seems to be broken (DHTML again).
When going on to "Infrastruktur" a message is displayed from time to time (this
should not occur). It works pretty fine with versions < 1.2.
By the way: scrolling is terribily slow.

Reproducible: Always

Steps to Reproduce:
1. go http://www.actionscouts.com/ski/schladming-planai and try it with 1.1 and 1.2
2.
3.

Actual Results:  
starting the browser

Expected Results:  
a DHTML menu

Mozilla doesn't crash.
Confirming on NT SP6a: 
Left - Bottom DHTML menu does not show in Mozilla/5.0 (Windows; U; WinNT4.0;
en-US; rv:1.2) Gecko/20021126   
but does show in Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2b)
Gecko/20021029 Phoenix/0.4
WFM build 2002112304, Windows 2000. Submenues show up. Looks like garbage left
on the screen though
Confirming bug on 1.2.
José, were you using a 1.2- or tunk-build?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Tested on 1.3a nightly trunk 2002112708 and MSIE 6.0.26

Rendering speed was relatively slow, but it is a very complex page. Scrolling
speed is fine.

Page renders almost identically on Moz and MSIE.

Left-hand Menu renders and links and rollovers both work.

HOWEVER
   - Moz progress bar remains dark, near 100%, after page has loaded.
   - (DHTML) Drop-down menu ("Functionen") has unclickable menu items.
   - Javascript music control buttons possibly do not work (untested)

Using win2000 professional, Pentium 4.
> Javascript music control buttons possibly do not work (untested)

no surprise there.
http://www.actionscouts.com/js/music.js
function musicON() 
{
   var temp;
   
   //temp = "../../pics/bilder/breathe2.mid" 
   if (document.all)
   {
	document.all.sound.src = temp;
   }
}

--------------------------------
the menus display fine with linux trunk build 20021126 and 1.2 for me.
None of the submenu links in the top and left menu work properly. (similar to
bug 132592)

> When going on to "Infrastruktur" a message is displayed from time to time 

??  what message

For anybody still trying to find the "left" menu, it's at the bottom of the page
Page works fine with trunk build 2002112607. There seems to be some problems
with 1.2 and DHTML/JS, see bug 182466 and bug 182477, which also are 1.2 specific.

I bet the message mentioned in comment 0 is something like "There seems to be an
error with this layer:#Frame: [object Window]#Layer: divoCMenu0_0b.divoCMenu0_0"

Maybe we need moz 1.2.1?
What we need is a testcase...
I'm having trouble doing a DNS lookup on www.actionscouts.com, but this really
seems like it's related to bug 182500.
Version: Trunk → Other Branch
I also think this is caused by bug 182500, since that bug causes 
bug 182253, "document.write() eats initial characters in 1.2"

Any site that creates DHTML menus via document.write() will 
therefore be affected. Compare other bugs where DHTML menus
no longer work on the 1.2 branch only, listed as dependencies
of bug 182500.

Reassigning to Parser for parity with bug 182500 -
Assignee: asa → harishd
Component: Browser-General → Parser
Depends on: 182500
QA Contact: asa → moied
Whiteboard: [Bug only in 1.2 builds; site works with trunk builds]
If someone can test that this is fixed in the 1.2.1 release, please mark it fixed.
Site WFM now (1.2.1 final), marking as fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.