[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] [bug #37223] JavaScript call didn't reach the ExternalInt

From: Sandro Santilli
Subject: [Gnash-commit] [bug #37223] JavaScript call didn't reach the ExternalInterface callback
Date: Sat, 26 Dec 2015 14:48:19 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0

Follow-up Comment #22, bug #37223 (project gnash):

Ideally there would be a single test composed by one (or more) SWF files and
one (or more) HTML files so that anyone could point a web browser to the test
entry point and intuitively see what's failing what's succeeding and what's
running (test summary); then a test _runner_ would somehow simulate the html
interaction in an automated way (webkit-based, for example).

Failing to do that, an easier solution could be for the test runner to
generate an HTML file that would replicate what the test runner does and
contain instructions for the tester as for what's expected and what's

Note that all the tests under testsuite/actionscript.all are similar in this
regard (self-contained tests) but were simpler to implement because do not
require bidirectional host communication.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]