bugGnash - The GNU Flash player - Bugs: bug #47004, Gnash didn't pass string return...

 
 

bug #47004: Gnash didn't pass string return value "Error" and "SecurityError" from ExternalInterface callback

Submitter:  Nutchanon Wetchasit <nachanon>
Submitted:  Fri 29 Jan 2016 08:05:26 AM UTC
   
 
Category:  plugin Severity:  3 - Normal
Release:  master Status:  Ready For Test
Privacy:  Public Assigned to:  strk
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 27 Feb 2016 10:25:57 AM UTC, comment #14: 

ExternalInterface issues related to `Number` type are now tracked separately as bug #47280.

 Nutchanon Wetchasit <nachanon>
Sat 20 Feb 2016 06:53:06 AM UTC, comment #13: 

Patch included for fixing `null` return value and incorrect error messages;
see patch #8914.

This is text output of `js2flash-errorstring.html` on browser with patched Gnash:

Flash's error_call() returned type string, value: Error
Flash's securityerror_call() returned type string, value: SecurityError
Flash's hello_call() returned type string, value: Hello!


Debug log (verbosity 1 + action error) from the run:

87 SECURITY: Extensions disabled
88 UNIMPLEMENTED: FileAttributes tag in the SWF requests that network access is not granted to this movie (or application?) when loaded from the filesystem. Anyway Gnash won't care; use white/black listing in your .gnashrc instead
89 TRACE: callee: finished initializing
2931 TRACE: callee: error_call callback invoked
2941 TRACE: callee: securityerror_call callback invoked
2951 TRACE: callee: hello_call callback invoked


You'd see that there are no "ERROR: Couldn't process ExternalInterface Call..."
message appearing after `error_call()` and `securityerror_call()` callback
invocation anymore.

This is text output of `js2flash-rtypes.html` on browser with patched Gnash:

PASSED: Flash should properly register string_call callback
PASSED: Flash should properly register error_call callback
PASSED: Flash should properly register securityerror_call callback
PASSED: Flash should properly register integer_call callback
PASSED: Flash should properly register float_call callback
PASSED: Flash should properly register infinite_call callback
PASSED: Flash should properly register neginfinite_call callback
PASSED: Flash should properly register nan_call callback
PASSED: Flash should properly register boolean_call callback
PASSED: Flash should properly register null_call callback
PASSED: Flash should properly register noret_call callback
PASSED: Flash should properly register undefined_call callback
PASSED: Flash should properly register exception_call callback
PASSED: Flash should properly register array_call callback
PASSED: Flash should properly register object_call callback
PASSED: Flash should properly register object_customstring_call callback
PASSED: Flash should properly register object_customvalue_call callback
PASSED: Flash should properly register function_call callback
PASSED: Flash callback script_call should return a correct type
PASSED: Flash callback script_call should return a correct value
PASSED: Flash callback error_call should return a correct type
PASSED: Flash callback error_call should return a correct value
PASSED: Flash callback securityerror_call should return a correct type
PASSED: Flash callback securityerror_call should return a correct value
PASSED: Flash callback integer_call should return a correct type
PASSED: Flash callback integer_call should return a correct value
PASSED: Flash callback float_call should return a correct type
PASSED: Flash callback float_call should return a correct value
PASSED: Flash callback infinite_call should return a correct type
FAILED: Flash callback infinite_call should return a correct value ("0" != "Infinity")
PASSED: Flash callback neginfinite_call should return a correct type
FAILED: Flash callback neginfinite_call should return a correct value ("0" != "-Infinity")
PASSED: Flash callback nan_call should return a correct type
FAILED: Flash callback nan_call should return a correct value
PASSED: Flash callback boolean_call should return a correct type
PASSED: Flash callback boolean_call should return a correct value
PASSED: Flash callback null_call should return a correct type
PASSED: Flash callback null_call should return a correct value
PASSED: Flash callback noret_call should return a correct type
PASSED: Flash callback noret_call should return a correct value
PASSED: Flash callback undefined_call should return a correct type
PASSED: Flash callback undefined_call should return a correct value
PASSED: Flash callback exception_call should return a correct type
PASSED: Flash callback exception_call should return a correct value
FAILED: Flash callback array_call should return a correct type ("function" != "object")
FAILED: Flash callback array_call should return an object of Array class
FAILED: Flash callback array_call should return an array with correct size ("undefined" != "9")
FAILED: Flash callback array_call should return an array with correct element 0 ("undefined" != "The")
FAILED: Flash callback array_call should return an array with correct element 1 ("undefined" != "quick")
FAILED: Flash callback array_call should return an array with correct element 2 ("undefined" != "brown")
FAILED: Flash callback array_call should return an array with correct element 3 ("undefined" != "fox")
FAILED: Flash callback array_call should return an array with correct element 4 ("undefined" != "jumps")
FAILED: Flash callback array_call should return an array with correct element 5 ("undefined" != "over")
FAILED: Flash callback array_call should return an array with correct element 6 ("undefined" != "the")
FAILED: Flash callback array_call should return an array with correct element 7 ("undefined" != "lazy")
FAILED: Flash callback array_call should return an array with correct element 8 ("undefined" != "dog")
ERROR: Error: Error calling method on NPObject!


You'd see that return value from `null_call()` ExternalInterface callback
is now correctly seen from JavaScript as `null`.

Other failures regarding numeric return values are remaining
to be investigated, possibly as a separate report.

Gnash: 0.8.11dev (patched against git 051aa9c 15-Feb-2016) NPAPI
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386

Nutchanon Wetchasit <nachanon>
Sat 20 Feb 2016 03:52:05 AM UTC, comment #12: 

This is text output from `js2flash-rtypes.html` on browser with current Gnash:

PASSED: Flash should properly register string_call callback
PASSED: Flash should properly register error_call callback
PASSED: Flash should properly register securityerror_call callback
PASSED: Flash should properly register integer_call callback
PASSED: Flash should properly register float_call callback
PASSED: Flash should properly register infinite_call callback
PASSED: Flash should properly register neginfinite_call callback
PASSED: Flash should properly register nan_call callback
PASSED: Flash should properly register boolean_call callback
PASSED: Flash should properly register null_call callback
PASSED: Flash should properly register noret_call callback
PASSED: Flash should properly register undefined_call callback
PASSED: Flash should properly register exception_call callback
PASSED: Flash should properly register array_call callback
PASSED: Flash should properly register object_call callback
PASSED: Flash should properly register object_customstring_call callback
PASSED: Flash should properly register object_customvalue_call callback
PASSED: Flash should properly register function_call callback
PASSED: Flash callback script_call should return a correct type
PASSED: Flash callback script_call should return a correct value
PASSED: Flash callback error_call should return a correct type
PASSED: Flash callback error_call should return a correct value
PASSED: Flash callback securityerror_call should return a correct type
PASSED: Flash callback securityerror_call should return a correct value
PASSED: Flash callback integer_call should return a correct type
PASSED: Flash callback integer_call should return a correct value
PASSED: Flash callback float_call should return a correct type
PASSED: Flash callback float_call should return a correct value
PASSED: Flash callback infinite_call should return a correct type
FAILED: Flash callback infinite_call should return a correct value ("0" != "Infinity")
PASSED: Flash callback neginfinite_call should return a correct type
FAILED: Flash callback neginfinite_call should return a correct value ("0" != "-Infinity")
PASSED: Flash callback nan_call should return a correct type
FAILED: Flash callback nan_call should return a correct value
PASSED: Flash callback boolean_call should return a correct type
PASSED: Flash callback boolean_call should return a correct value
FAILED: Flash callback null_call should return a correct type ("string" != "object")
FAILED: Flash callback null_call should return a correct value ("Error" != "null")
PASSED: Flash callback noret_call should return a correct type
PASSED: Flash callback noret_call should return a correct value
PASSED: Flash callback undefined_call should return a correct type
PASSED: Flash callback undefined_call should return a correct value
PASSED: Flash callback exception_call should return a correct type
PASSED: Flash callback exception_call should return a correct value
FAILED: Flash callback array_call should return a correct type ("function" != "object")
FAILED: Flash callback array_call should return an object of Array class
FAILED: Flash callback array_call should return an array with correct size ("undefined" != "9")
FAILED: Flash callback array_call should return an array with correct element 0 ("undefined" != "The")
FAILED: Flash callback array_call should return an array with correct element 1 ("undefined" != "quick")
FAILED: Flash callback array_call should return an array with correct element 2 ("undefined" != "brown")
FAILED: Flash callback array_call should return an array with correct element 3 ("undefined" != "fox")
FAILED: Flash callback array_call should return an array with correct element 4 ("undefined" != "jumps")
FAILED: Flash callback array_call should return an array with correct element 5 ("undefined" != "over")
FAILED: Flash callback array_call should return an array with correct element 6 ("undefined" != "the")
FAILED: Flash callback array_call should return an array with correct element 7 ("undefined" != "lazy")
FAILED: Flash callback array_call should return an array with correct element 8 ("undefined" != "dog")
ERROR: Error: Error calling method on NPObject!


You'd see that libgnashplugin didn't crash at integer Number access anymore
(the remaining crash likely to be bug #37223). But there's one unexpected
wrong result; ExternalInterface callback `null_call` is now returning
"Error" string instead of `null`.

According to player-to-container communication dump which shown
`<string>Error</string>` return value from `null_call`, this is likely due to
leftover in-band error flag generation in Gnash (player); narrowed down to
code in `movie_root::callExternalCallback()` around line 1964:

    std::string result;
    if (val.is_null()) {
        // Return an error
        result = ExternalInterface::makeString("Error");
    } else {
        result = ExternalInterface::toXML(val);
    }


This flags legitimate `null` return value from ActionScript callback as
an error, and send it to libgnashplugin as in-band "Error" string indicator.
(It doesn't turn back to `null` before reaching JavaScript as in-band
ExternalInterface error signalling is now dropped from libgnashplugin)

Output, logs, backtraces, and screenshots from testing
`js2flash-errorstring.html`, `flash2js-errorstring.html`, `js2flash-rtypes`,
and `flash2js-rtypes` are attached as `jsflash-errorstring-rtypes_roundup.051aa9c.zip`.

Gnash: 0.8.11dev (git 051aa9c 15-Feb-2016) NPAPI
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386


(file #36405)

 Nutchanon Wetchasit <nachanon>
Sat 20 Feb 2016 03:43:20 AM UTC, comment #11: 

This is text output from `js2flash-errorstring.html` on browser with current Gnash:

Flash's error_call() returned type string, value: Error
Flash's securityerror_call() returned type string, value: SecurityError
Flash's hello_call() returned type string, value: Hello!


Gnash's debug output (verbosity 1) from the run:

98 SECURITY: Extensions disabled
98 UNIMPLEMENTED: FileAttributes tag in the SWF requests that network access is not granted to this movie (or application?) when loaded from the filesystem. Anyway Gnash won't care; use white/black listing in your .gnashrc instead
99 TRACE: callee: finished initializing
2950 TRACE: callee: error_call callback invoked
2951 ERROR: Couldn't process ExternalInterface Call error_call
2961 TRACE: callee: securityerror_call callback invoked
2961 ERROR: Couldn't process ExternalInterface Call securityerror_call
2971 TRACE: callee: hello_call callback invoked


You'd see that the value returned to JavaScript is now correct, but there are
some odd "ERROR: Couldn't process ExternalInterface Call..." messages
appearing in the debug output.

This could be narrowed down to Gnash (player)'s ExternalInterface callback
handling code function `movie_root::processInvoke()` in `libcore/movie_root.cpp` around line 1683:

        std::string result = callExternalCallback(invoke->name, invoke->args);
        if (result == ExternalInterface::makeString("Error")) {
            return false;
        } else if (result == ExternalInterface::makeString("SecurityError")) {
            return false;
        }
        return true;


This flags legitimate "Error" and "SecurityError" string return value from
callback as error and returned `false` from the `movie_root::processInvoke()`
function, triggering error message.

This doesn't affect return value seen from JavaScript as `movie_root::callExternalCallback()` already sent it to host container.

Gnash: 0.8.11dev (git 051aa9c 15-Feb-2016) NPAPI
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386

Nutchanon Wetchasit <nachanon>
Mon 15 Feb 2016 10:37:11 AM UTC, comment #10: 

Ready for test as patch #8909 have been applied

 Sandro Santilli <strk>
Group Member
Sun 14 Feb 2016 11:20:39 AM UTC, comment #9: 

I have written another set of test SWF/HTML file (compiles on MTASC),
which try to check on how Flash return value of various types from
ExternalInterface (in both direction).

JavaScript calls Flash direction: attached as `js2flash-rtypes.zip`.
Flash calls JavaScript direction: attached as `flash2js-rtypes.zip`.

Note: There seems to be some peculiarities regarding how Flash Player
deal with odd return values:

  • `Infinity` and `-Infinity` value:
    • In JavaScript-calls-Flash scenario, they were returned properly.
    • In Flash-calls-JavaScript scenario, they were returned as NaN.
  • Function-typed field in `Object` return value:
    • In JavaScript-calls-Flash scenario, it refused to return the entire object; returned `null` instead.
    • In Flash-calls-JavaScript scenario, the object itself is returned properly, though its function-typed fields were set to `null`.


Gnash: 0.8.11dev (git 435d3e9 6-Feb-2016) NPAPI
Flash Player: 11.2 r202 (11.2.202.491) NPAPI binary
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386


(file #36330, file #36331)

 Nutchanon Wetchasit <nachanon>
Mon 08 Feb 2016 09:54:29 AM UTC, comment #8: 

Refer to task #5919 for the "protocol". I'm not sure it was ever fully specified, but that task would be the place to further discuss specifications, I'd think.

 Sandro Santilli <strk>
Group Member
Sun 07 Feb 2016 12:43:23 PM UTC, comment #7: 

Also, there seems to be some mismatching interpretation of `undefined` value
in Gnash's ExternalInterface implementation:

                            | NPAPI libgnashplugin   | Gnash (player)
============================+========================+=======================
Flash returns to JavaScript | <void/> [1]            | <undefined/> [2]
JavaScript returns to Flash | <void/> [3]            | <void/> [4]


According to the table, the marshalling result of JavaScript and
ActionScript's `undefined` value is supposed to be "<void/>". As current
container-emulated tests are currently interpreting `undefined` as
"<undefined/>", not "<void/>" (following current Gnash player's output),
it would need to be adjusted when this bug is fixed.

Side note: `GetVariable()` plugin function and associated tests are not
affected by this discrepancy as the function does not return `undefined` value.

Gnash: 0.8.11dev (git 435d3e9 6-Feb-2016)
System: Debian GNU/Linux 7.0 Wheezy i386

[1] http://git.savannah.gnu.org/cgit/gnash.git/tree/plugin/npapi/external.cpp?id=435d3e9aa7864883f6a2379fd318126113786475#n286
[2] http://git.savannah.gnu.org/cgit/gnash.git/tree/libcore/ExternalInterface.cpp?id=435d3e9aa7864883f6a2379fd318126113786475#n117
[3] http://git.savannah.gnu.org/cgit/gnash.git/tree/plugin/npapi/external.cpp?id=435d3e9aa7864883f6a2379fd318126113786475#n377
[4] http://git.savannah.gnu.org/cgit/gnash.git/tree/libcore/ExternalInterface.cpp?id=435d3e9aa7864883f6a2379fd318126113786475#n245

Nutchanon Wetchasit <nachanon>
Sun 07 Feb 2016 12:25:52 PM UTC, comment #6: 

Does Gnash's container-player XML communication protocol is implemented to
conform to some kind of specification?

I'd like to know if said spec has provision for exception handling in
remote procedure call, so I could implement them properly.

Alternatively, this could be implemented in a way that exception would
be turned into to `undefined` return value before sending it back to the
calling party. (Which is also a correct behavior as much as JavaScript
and ActionScript are concerned)

Nutchanon Wetchasit <nachanon>
Sat 06 Feb 2016 12:19:43 PM UTC, comment #5: 

This is another test SWF file (created with MTASC again) to show difference
on ExternalInterface exception handing between Flash player and Gnash,
but in Flash-calls-JavaScript direction.

Text output from running `flash2js-exception.html` under browser with Flash Player:

JavaScript's exception_call function is called.


Player's trace output from the run:

Warning: Reference to undeclared variable, 'Flash2JSException'
caller: JavaScript's exception_call() returned type undefined, value: undefined


You'd see that ActionScript side got `undefined` return value when JavaScript side thrown exception.

Text output from running `flash2js-exception.html` under browser with Gnash:

JavaScript's exception_call function is called.


Gnash's debug output from the run:

69 SECURITY: Extensions disabled
69 ACTIONSCRIPT ERROR: reference to non-existent variable 'Flash2JSException'
71 TRACE: VAL: [string:Error]
71 TRACE: caller: JavaScript's exception_call() returned type undefined, value: undefined


You'd see that ActionScript side also got `undefined`, which is correct.
But container-player communication dump shown that libgnashplugin sent
following return value to Gnash player:

<string>Error</string>


This is indistinguishable from ordinary string "Error" return value,
causing the problem that previously mentioned in comment 2.

Test SWF, source code, HTML container, build script, text output and logs
are attached as `flash2js-exception.zip`.

Gnash: 0.8.11dev (git 02ec1e6 3-Feb-2016)
Flash Player: 11.2 r202 (11.2.202.491) NPAPI binary
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386


(file #36267)

 Nutchanon Wetchasit <nachanon>
Sat 06 Feb 2016 12:01:28 PM UTC, comment #4: 

I also made a test SWF file (using MTASC) to show difference on how Flash
and Gnash handle exception in ExternalInterface, in JavaScript-calls-Flash direction.

Text output from running `js2flash-exception.html` under browser with Flash Player:

Flash's exception_call() returned type undefined, value: undefined


Player's trace output from the run:

Warning: Reference to undeclared variable, 'JS2FlashException'
callee: finished initializing
callee: exception_call callback is called
Warning: Uncaught exception, This is a test Error


You'd see that JavaScript side got `undefined` return value when ActionScript side thrown exception.

Text output from running `js2flash-exception.html` under browser with Gnash:

Flash's exception_call() returned type object, value: null


Gnash's debug output from the run:

76 SECURITY: Extensions disabled
76 ACTIONSCRIPT ERROR: reference to non-existent variable 'JS2FlashException'
77 TRACE: callee: finished initializing
2940 TRACE: callee: exception_call callback is called


You'd see that JavaScript side got `null` when ActionScript side thrown
exception. According to container-player communication dump, Gnash (player)
correctly sent `<undefined/>` return value to libgnashplugin.

Test SWF, source code, HTML container, build script, text output and logs
are attached as `js2flash-exception.zip`.

Gnash: 0.8.11dev (git 02ec1e6 3-Feb-2016)
Flash Player: 11.2 r202 (11.2.202.491) NPAPI binary
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386


(file #36266)

 Nutchanon Wetchasit <nachanon>
Sat 06 Feb 2016 11:38:33 AM UTC, comment #3: 

I have done some additional check on ExternalInterface's error condition
regarding exception, I found that with Flash Player plugin...

  • When JavaScript called ActionScript function and it threw exception: JavaScript would just get `undefined` return value, without exception thrown.
  • When ActionScript called JavaScript function and it threw exception: ActionScript would just get `undefined` return value, without exception thrown.


Flash Player: 11.2 r202 (11.2.202.491) NPAPI binary
Browser: Iceweasel 10.0.12
System: Debian GNU/Linux 7.0 Wheezy i386

Nutchanon Wetchasit <nachanon>
Mon 01 Feb 2016 05:27:31 AM UTC, comment #2: 

This issue is not limited to JavaScript-calls-Flash direction,
Flash-calls-JavaScript direction (`ExternalInterface.call()`) has the
similar problem.

I have made a test SWF (using libming's makeswf) that tries to call three
JavaScript functions which return string "Error", "SecurityError", and
"Hello!" to demonstrate this issue:

Trace output from running `flash2js-errorstring.html` under browser with Flash Player:

caller: JavaScript's error_call() returned type string value: Error
caller: JavaScript's securityerror_call() returned type string value: SecurityError
caller: JavaScript's hello_call() returned type string value: Hello!


You'd see that string "Error", "SecurityError", and "Hello!" are passed back
to ActionScript correctly.

Log output from running `flash2js-errorstring.html` under browser with Gnash:

81 SECURITY: Extensions disabled
81 UNIMPLEMENTED: FileAttributes tag in the SWF requests that network access is not granted to this movie (or application?) when loaded from the filesystem. Anyway Gnash won't care; use white/black listing in your .gnashrc instead
107 TRACE: VAL: [string:Error]
107 TRACE: caller: JavaScript's error_call() returned type undefined value: undefined
108 TRACE: VAL: [string:SecurityError]
108 TRACE: caller: JavaScript's securityerror_call() returned type undefined value: undefined
119 TRACE: caller: JavaScript's hello_call() returned type string value: Hello!


You'd see that "Error", and "SecurityError" string are passed back to
ActionScript as `undefined`, which is incorrect. Also, there are unknown
"VAL: " trace messages popped-up too.

According to container-player communication dump, each "<string>" return value
are correctly sent from libgnashplugin. So this side of the issue is likely
to be Gnash (player)'s fault.

Test SWF, HTML container, source code, build script, screenshots, logs, and
container-player communication dump are attached as `flash2js-errorstring.zip`.

Gnash: Gnash 0.8.11dev (git e705394 29-Jan-2016) NPAPI
Flash Player: 11.2 r202 (11.2.202.491) NPAPI binary
Browser: Iceweasel 10.0.12
System: Debian GNU/Linux 7.0 Wheezy i386


(file #36226)

 Nutchanon Wetchasit <nachanon>
Sun 31 Jan 2016 02:49:37 AM UTC, comment #1: 

This problem could be narrowed down to `plugin/npapi/callbacks.cpp`, inside
function `remoteCallback()` around line 707:

    std::string answer;
    GnashNPVariant parsed = plugin::ExternalInterface::parseXML(data);
    if (!NPVARIANT_IS_NULL(parsed.get())) {
        answer = NPStringToString(NPVARIANT_TO_STRING(parsed.get()));
    }
    if (answer == "Error") {
        NULL_TO_NPVARIANT(*result);
    } else if (answer == "SecurityError") {
        NULL_TO_NPVARIANT(*result);
    } else {
        parsed.copy(*result);
    }


This check doesn't seem appropriate, as:

  • It fails when ActionScript's callback legitimately returned a string "Error" or "SecurityError"; demonstrated by test file.
  • Bad things could happen if the return value is both not `null` and is not a String. (e.g. `NPObject`)


Second one is actually the reason I found this issue in the first place;
this string conversion code crashes when I tried to make
`ExternalInterface::parseXML()` return a full-blown `NPObject` derived
from JavaScript `Object` (a part of bug #32411's fix).

Gnash: Gnash 0.8.11dev (git e705394 29-Jan-2016) NPAPI
Browser: Iceweasel 10.0.12
System: Debian GNU/Linux 7.0 Wheezy i386

Nutchanon Wetchasit <nachanon>
Fri 29 Jan 2016 08:05:26 AM UTC, original submission:  

This is a spin-off from bug #37223 (ExternalInterface registration issue),
and bug #32411 (ExternalInterface Object data issue).

There is a weird problem in libgnashplugin's ExternalInterface callback
return value handling. I found that if a string "Error", or "SecurityError"
is returned from Flash-side callback, JavaScript would get `null` value
instead of the returned string. Other string values are passed correctly.

I have created simple SWF file (Flash 8) using libming's makeswf, which
registers a callback named `error_call` and `securityerror_call` and
`hello_call` which return string "Error", "SecurityError", and "Hello!"
to demonstrate this problem.

Text output from running `js2flash-errorstring.html` under browser with Flash Player:

Flash's error_call() returned type string, value: Error
Flash's securityerror_call() returned type string, value: SecurityError
Flash's hello_call() returned type string, value: Hello!


You'd see that string "Error", "SecurityError", and "Hello!" are passed back
to JavaScript correctly.

Text output from running `js2flash-errorstring.html` under browser Gnash:

Flash's error_call() returned type object, value: null
Flash's securityerror_call() returned type object, value: null
Flash's hello_call() returned type string, value: Hello!


You'd see that "Error", and "SecurityError" string are passed back to
JavaScript as `null`, which is incorrect.

According to container-player communication dump, each "<string>" value
are correctly sent from Gnash's player side. So this is most likely to be
libgnashplugin's fault.

SWF file, source code, build script, HTML container, screenshots, text output
debug logs, and container-player communication dumps are attached as `js2flash-errorstring.html`.

Gnash: 0.8.11dev (git 62cfdfe 16-Jan-2016) NPAPI
Flash Player: 11.2 r202 (11.2.202.491) NPAPI binary
Browser: Iceweasel 10.0.12 (debian)
System: Debian GNU/Linux 7.0 Wheezy i386

Nutchanon Wetchasit <nachanon>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #36405:  jsflash-errorstring-rtypes_roundup.051aa9c.zip added by nachanon (29KiB - application/zip - Output, logs, and backtraces from error string and return type tests on Gnash 0.8.11dev git 051aa9c)
file #36330:  js2flash-rtypes.zip added by nachanon (42KiB - application/zip - Multiple return type test Flash files (Flash calls JavaScript and JavaScript calls Flash), HTML containers, source codes, screenshots, and logs)
file #36331:  flash2js-rtypes.zip added by nachanon (15KiB - application/zip - Multiple return type test Flash files (Flash calls JavaScript and JavaScript calls Flash), HTML containers, source codes, screenshots, and logs)
file #36267:  flash2js-exception.zip added by nachanon (6KiB - application/zip - Test Flash file (Flash calls JavaScript, throwing Error), HTML container, source code, screenshots and logs)
file #36266:  js2flash-exception.zip added by nachanon (7KiB - application/zip - Test Flash file (JavaScript calls Flash, throwing Error), HTML container, source code, screenshots and logs)
file #36226:  flash2js-errorstring.zip added by nachanon (7KiB - application/zip - Test Flash file (Flash-calls-JavaScript), HTML container, source code, screenshots and logs)
file #36194:  js2flash-errorstring.zip added by nachanon (9KiB - application/zip - Test Flash file, HTML container, source code, screenshots and logs)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by strk (Posted a comment)
  • -email is unavailable- added by nachanon (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 9 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-02-20 nachanon Attached File- Added jsflash-errorstring-rtypes_roundup.051aa9c.zip, #36405
    2016-02-15 strk StatusNone Ready For Test
        Assigned toNone strk
    2016-02-14 nachanon Attached File- Added js2flash-rtypes.zip, #36330
        Attached File- Added flash2js-rtypes.zip, #36331
    2016-02-06 nachanon Attached File- Added flash2js-exception.zip, #36267
    2016-02-06 nachanon Attached File- Added js2flash-exception.zip, #36266
    2016-02-01 nachanon Attached File- Added flash2js-errorstring.zip, #36226
    2016-01-29 nachanon Attached File- Added js2flash-errorstring.zip, #36194

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-5884.
    Corresponding source code