264391 - Forms unresponsive when javascript updates title

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Sigve Indregard]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

The webpage (www.solofondet.no) updates the titlebar clock (!) every second. It
works quite all right for normal pages, but the form hidden behind the link
"s&oring;knadsskjemaet" in the third paragraph is completely unresponsive.
(Sorry, I can't link it directly, the server seems to redirect all requests to
start.htm).

Disabling javascript, the site works perfectly, but the clock obviously stops.
Not that it hurts to lose the clock, but a less experienced user would never
find out that javascript was the problem.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Sigve Indregard]

Attachment: The abusive javascript

This javascript updates the titlebar with the current time and date. Copyright
@ctiveWEB. Available from http://www.solofondet.no/include/klokke_dato.js

Comment 2

[Martijn Wargers (dead)]

It is more likely because of bad js code, see:
http://www.solofondet.no/include/general.js

document.oncontextmenu = function(){return false}
if(document.layers) {
window.captureEvents(Event.MOUSEDOWN);
window.onmousedown = function(e){
if(e.target==document)return false;
}
}
else {
document.onmousedown = function(){return false}
}

This: document.onmousedown = function(){return false}
means that all onmousedown events are not continued. That's why clicking on a
form control doesn't focus it. But you can tab through the form controls, however.

So I think this is more a tech evangelism issue.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.