227552 - primestore.it - Javascript handling problems

Status: RESOLVED INCOMPLETE

(Tech Evangelism Graveyard :: Italian, defect)

Description

[Nemo]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031120 Firebird/0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031120 Firebird/0.7

I'm sorry for non component specification. I'm not an expert. The problem
appears in several site that use more javascript functions.
I've provided an example URL. I don't know where is the problem, but I know
other browser (such as Opera) display the example URL (www.primestore.it)
without problems.
I'm sorry for poor technical details.

Reproducible: Always

Steps to Reproduce:
1.Use javascript menus, javascript functions
2.
3.

Actual Results:  
The features I want use do not respond.

Expected Results:  
Mozilla do nothing.

Comment 1

[Gérard Talbot]

I don't use Linux. Nevertheless, as far as I can see, the problems are
exclusively with the markup code, the design of the page, the DOM references and
the DHTML coding practices.

From the start, Mozilla will assign 0 to these 2 variables
var ns4up = (document.layers) ? 1 : 0;  
var ie4up = (document.all) ? 1 : 0;
and then will ignore several DHTML functions and forking code because Mozilla
does not support proprietary DOMs but only W3C DOM methods. (Nowhere does the
page test for support of getElementById or any other W3C DOM method.) So, for
instance, the whole "snow flakes" effects will not appear. Also, unrequested
popup windows might be filtered by Mozilla (ie.:
<script>apri_finestra()</script> while loading the page).

Finally, I tried the page with both MSIE 6 SP1 and Opera 7.23 and the window
task manager reported in both cases that the cpu activity was above 90% both
during loading of the page and *after* the loading of the page (most likely due
to the snowflakes effect): var speed = 2; ... setTimeout("snowIE()", speed);

I tried several links in the page (menus and the webpages loaded fine in all cases.

For many reasons (deprecated elements, deprecated attributes, invalid code (1207
errors if you choose HTML 4.01 transitional), table design, nested tables,
overconstrained tables, outdated DHTML coding practices, overall very demanding
cpu and RAM functions, absence of specifics in the description of the bug), I
suggest to resolve this bug as INVALID. 

Comment 2

[Boris Zbarsky [:bzbarsky]]

Over to evang, actually.  The use of document.all/document.layers exclusively
needs to be evangelized....

For future information, Opera implements the document.all IEism, sort of.  So
some sites that use it may work in Opera.

Comment 3

[Riccardo Cretti]

The OS should be changed to All.

Comment 4

[Chris Lawson (gone)]

INCOMPLETE due to lack of activity since the end of 2009.

If someone is willing to investigate the issues raised in this bug to determine whether they still exist, *and* work with the site in question to fix any existing issues, please feel free to re-open and assign to yourself.

Sorry for the bugspam; filter on "NO MORE PRE-2010 TE BUGS" to remove.