[Gnash-commit] [bug #32411] ExternalInterface XML parser fails with nested tags

[Nutchanon Wetchasit]

Follow-up Comment #23, bug #32411 (project gnash):

I have been looked around Gnash's NPAPI tester for a while, it seems that
making an automated test works for this case might be difficult, since in
current libgnashplugin testing environment
<http://git.savannah.gnu.org/cgit/gnash.git/tree/plugin/npapi/test.cpp?id=c12c3cf104a095cff9791cdb3cee8bbf4853d5e0>:
* Standalone tester doesn't seem to have access to the
`GnashPluginScriptObject` and `NPP` plugin instance.
* Standalone tester doesn't seem to have access to an JavaScript environment;
calling host's `window.Object()` wouldn't work.

I'm not sure how real the NPAPI environment would need to be in order to run
these tests with meaningful result. (A lot of things could be emulated,
but they might not work the same as a real browser).

>From current experimental fix `plugin-return-js-object-v2.patch`, one
possible
stopgap measure is passing `NULL` as an `GnashPluginScriptObject` parameter
of `ExternalInterface::parseXML()`. This allows non-Object non-Array parsing
tests to continue working, but provide no real support for actually testing
this issue in automated way.

Updated `plugin-return-js-object-v2.patch` with this stopgap measure applied,
is included as patch #8916.

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


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32411>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/