If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Javascript unable to talk to Cult3D object

RESOLVED EXPIRED

Status

()

Core
Plug-ins
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Laurynas Butkus, Assigned: Peter Lubczynski)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007

It seems that Javascript cannot communicate with Cult3D object. On Mozilla 1.4
RC1   this Cult3D worked fine.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
When clicking "Atidaryti sliauzikli" and "Ijungti rodomaja programa" nothing
happens.

Expected Results:  
Phone in Cult3D should rotate, open and so on..

Comment 1

14 years ago
Not a JavaScript Engine issue. The Engine is only concerned with the
behavior of JavaScript as a self-contained language.

The interaction between the JavaScript Engine and other parts of the
browser are the responsibility of those components.

Reassigning to Plug-ins component for further triage -
Assignee: general → peterlubczynski-bugs
Component: JavaScript Engine → Plug-ins

Comment 2

14 years ago
Laurynas:

Are there any errors in Tools > Web Development > JavaScript Console?
(be sure to clear it of any previous errors first)

Thanks; that will help us figure this out -

Comment 3

14 years ago
Setting default QA -
QA Contact: PhilSchwartau → general
(Reporter)

Comment 4

14 years ago
JS Console shows following error:

Error: this.Cult3D.triggerAction is not a function
Source File:
http://www.nokia.lt/images/phones/models/n8910i/cult3d/scripts/cult3d.js
Line: 71
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.