History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: LPP-4695
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: P1 P1
Assignee: Max Carlson
Reporter: André Bargull
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
OpenLaszlo

Runtime-Exception in IE with Flash8

Created: 10/Sep/07 09:37 AM   Updated: 12/Sep/07 02:17 PM
Component/s: Browser Integration
Affects Version/s: 4.0.5WaffleCone
Fix Version/s: 4.0.5WaffleCone

Time Tracking:
Not Specified

Severity: Major
Fixed in Change#: 6,448
Runtime: N/A
Fix in hand: False


 Description  « Hide
I get the following runtime-exception in IE6 with Runtime-Target Flash8:
"The object does not support this property or method"

First at line 0:
try { lzapp.SetReturnValue(__flash__toXML(dojo.flash.comm._addExternalInterfaceCallback("getCanvasAttribute")) ); } catch (e) { lzapp.SetReturnValue("<undefined/>"); }

When I inspect "lzapp" with the ScriptDebugger, I don't see any "SetReturnValue"-method...


After happily clicking away all the warnings in IE, I get the same warning later again on line 453:
,_execFlash:function($1,$2){
var $3=dojo.flash.obj.get()
$3.startExec() <== this throws the error
$3.setNumberArguments($2.length)
for(var $4=0;$4<$2.length;$4++){
this._chunkArgumentData($2[$4],$4)
}
$3.exec($1)
var $5=this._chunkReturnData()
$5=this._decodeData($5)
$3.endExec()
return $5
}

With the ScriptDebugger, I've found out that "$3" is the "lzapp"-object, but it does not have any "startExec" and co methods.


As I said, this does only happen in IE6 with Flash8 as the Runtime-Target, Flash7 works perfectly. Firefox2 and Opera9 work seamlessly in all runtimes.
And I couldn't reproduce this error in OpenLaszlo4.0.3, it is a "wafflecone"-only thing.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Max Carlson - 11/Sep/07 06:38 PM
This needs to get fixed. It sounds like the issue Lorien is seeing with history...

Max Carlson - 12/Sep/07 09:30 AM
this happened as of r6256. A workaround is to load the application with ?lzt=html.