Closed
Bug 101259
Opened 24 years ago
Closed 24 years ago
ao.net - Javascript clock not functioning
Categories
(Tech Evangelism Graveyard :: English US, defect, P4)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
VERIFIED
FIXED
Nov
People
(Reporter: rockowallaby, Assigned: bc)
References
()
Details
Attachments
(1 file)
|
3.25 KB,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:0.9.4) Gecko/20010918
BuildID: 2001091812
There is a Javascript clock on the URL that is supposed to update on it's
own. It works on IE and other versions of Netscape (except Mozilla). On
Mozilla (for OS/2) nothing appears.
I don't have other platforms around I can test this on to see if it's a specific
platform, so maybe someone can help me there.
Reproducible: Always
Steps to Reproduce:
Go to that URL :)
Actual Results: No clock
Expected Results: Clock appears and updates by itself
Comment 1•24 years ago
|
||
This happens on Windows as well, although it doesn't work for me on 4.x. It does
work on IE.
I'm moving it to Browser General so that someone in QA can classify it.
I'm not sure where it belongs.
Assignee: attinasi → asa
Status: UNCONFIRMED → NEW
Component: Layout → Browser-General
Ever confirmed: true
OS: OS/2 → All
QA Contact: petersen → doronr
Comment 2•24 years ago
|
||
if (!document.all)
return
-> evangelism (note that the dhtml effect works fine, just the clock is the
issue). The clock code would easily work in ns6 (innerHtml is used).
Assignee: asa → bclary
Component: Browser-General → English: US
Product: Browser → Tech Evangelism
QA Contact: doronr → zach
Version: other → unspecified
| Assignee | ||
Comment 3•24 years ago
|
||
Rocko, since you are the reporter I will mark this assigned to show you have
been contacted. Is there anything else you need to add support for Mozilla ?
Status: NEW → ASSIGNED
Priority: -- → P4
Summary: Javascript clock not functioning → ao.net - Javascript clock not functioning
Target Milestone: --- → mozilla0.9.6
| Reporter | ||
Comment 4•24 years ago
|
||
I origanally reported this thinking it was a bug! I didn't realize it was
simply not implemented.
While I don't personally see that sort of Javascript code used very often, I
suppose just to make Mozilla complete, support for that kind of code would be an
addition to consider.
I'm just using Mozilla as my everyday browser, and when I find things that don't
look right or cause it to crash I report it.
| Assignee | ||
Comment 5•24 years ago
|
||
| Assignee | ||
Comment 6•24 years ago
|
||
Note that the exclusion of Mozilla in the clock update was only one of the
problems. The other was the use of undeclared references to elements with id
attributes. In Mozilla you must explicitly obtain a reference to an element
before accessing it. Please see the previous attachment with the code to obtain
a reference to the tick2 element.
Marking fixed to get off the radar.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 7•24 years ago
|
||
Forgot to verify this a lot earlier. Sorry!
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•