Closed Bug 338630 Opened 18 years ago Closed 17 years ago

Error calling method on NPObject!

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
All
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: philip.chee, Unassigned)

References

(
URL
)

Details

(Keywords: regression) 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060519 Minefield/3.0a1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060519 MultiZilla/1.8.2.0e Mnenhy/0.7.4.0 SeaMonkey/1.5a

Error: Error calling method on NPObject!
Source file: chrome://flashblock/content/flashblock.xml
Line: 41

Steps to reproduce:
1. Install latest Flashblock-cvs from:
   <http://downloads.mozdev.org/flashblock/flashblock-1.5.unstable.xpi>
2. Restart Minefield.
3. Visit test case:
   <http://bugzilla.mozdev.org/attachment.cgi?id=3667&action=view>

Error occurs when we try to invoke a Flash method via javascript:
StopPlay() should be accessible via javascript.

function flashblockShowPlaceholder() {
	// Just in case the object has been moved away from under our feet during
	// the timeout, re-assign the parent node. See bug 13680
	parent = current.parentNode;
	parent.insertBefore(placeholder, current);
	if(placeholder.isStandalone) {
		placeholder.flashblock = "frame";
		current.StopPlay();

I have used the following web page to verify that flash scripting is working:
<http://www.adobe.com/support/flash/ts/documents/java_script_comm/javascript_to_flash.html?sendText=test>
so the flashplayer.xpt is registered and working.
Additional information:

Shockwave Flash
    File name: NPSWF32.dll
    Shockwave Flash 8.0 r24

Problem is trunk only. Current nightly builds for SeaMonkey 1.0.x and Firefox 1.5.0.x do not exihibit this problem.
Flags: blocking1.9a1? → blocking1.9a1+
So... I can't seem to reproduce this on Linux, since the Flash I have seems to have no working scripting, per end of comment 0.  I certainly never get this message.  :(

I doubt the box object patch would cause this, but then again I see nothing in the checkin range that _would_ cause this... :(  Could someone who can reproduce this try backing our the box object patch?  And maybe bug 335333?
> So... I can't seem to reproduce this on Linux, since the Flash I have seems
> to have no working scripting, per end of comment 0.  I certainly never get
> this message.

Is flashplayer.xpt present in your plugins directory?
Flags: blocking1.9a1+
Whiteboard: [blocking1.9a1+]
Vladimir, the blocking flag should be minused (I think)

With the latest minefield (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061102 Minefield/3.0a1) and the latest Flashblock this error does not occur.

With my test case:
<http://bugzilla.mozdev.org/attachment.cgi?id=3667&action=view>
I get the following error:
Error: uncaught exception: Permission denied to call method Location.toString
Which is bug 313115

With martijn's test case:
<http://wargers.org/mozilla/bug338630/mazda-test_iframe.html>
I don't get any errors.

The difference is that martijn has a <head></head>

So this bug is either WORKSFORME or should be duped to bug 313115
Flags: blocking1.9+ → blocking1.9?
Whiteboard: [blocking1.9a1+]
is the problem here just that you're seeing an error? Or is the flash errorously not working when it used to before?

If this is just about seeing an error then this is not a blocker. Otherwise please renominate
Flags: blocking1.9? → blocking1.9-
The problem is that calling the plug-in's methods throws instead of doing what it should do.
Flags: blocking1.9- → blocking1.9?
Jst says that the problem bz's seeing is unrelated to this bug since the flash player version that uses .xpt files and all that doesn't use NPObjects at all.

Minusing per this and comment 6. If someone still sees this please renominate.
Flags: blocking1.9? → blocking1.9-
Marking this WORKSFORME per comment #6.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.