Thanks Josh, I'll check out those options at some point. The FF ESR version I have was the last to officially support Flash player as extended browser support until (iirc) mid-2021.
I have some old Royale UI unit testing approaches that run swf and js testing side-by-side in the browser, which I still use before migrating the tests to the RoyaleUnit testing. The main advantage with keeping something that works in the browser is use of the ExternalInterface api, which is quite common (so far) in legacy apps we've been porting, so I sometimes need to check behaviour with that. I also had a graphics api side-by-side tester that let you issue console commands to use the flash drawing api in the flash player and the royale emulation of it side-by-side simultaneously, for example, using ExternalInterface also. I sometimes still fire that up. Outside of that, I'd agree that it's not 'needed' and perhaps my main reason for hanging on to it is mostly nostalgia - I started with Flash player 4 :) On Sat, Dec 18, 2021 at 6:16 AM Josh Tynjala <joshtynj...@bowlerhat.dev> wrote: > I wonder if you could download the same version of Firefox in "portable" > form? > > https://portableapps.com/apps/internet/firefox_portable/legacy > > If that still works with the Flash Player plugin, that would allow you to > keep your main installation up to date. > > Personally, I've uninstalled the Flash Player plugin completely, and I > haven't run into any strange situations where I wished I still had it. I've > been using the standalone debug executable of Flash Player instead, which > you can still download from Adobe, and that's been fine for my needs. Is > there any particular reason why you need the plugin specifically? > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > > > On Fri, Dec 17, 2021 at 1:45 AM Greg Dove <greg.d...@gmail.com> wrote: > > > btw I'm actually back a bit with FF 78.11.0esr (32-bit) which is pretty > > much from around 1 year ago. I am actually reluctant to upgrade this one, > > because it still runs the debug flash player in the browser, I think an > > upgrade is a one way street. > > > > > > On Fri, Dec 17, 2021 at 10:39 PM Greg Dove <greg.d...@gmail.com> wrote: > > > > > > > > OK thanks, I will double-check that. I was kinda focused on the "Error: > > > Channel closing: too late" > > > and thinking that was the cause, but obviously not :) > > > > > > > > > On Fri, Dec 17, 2021 at 10:28 PM Edward Stangler < > estang...@bradmark.com > > > > > > wrote: > > > > > >> > > >> Not really. This is how mine ends (Firefox 95.0 64-bit on Windows 10 > > >> 21H2): > > >> > > >> [java] RESULT: > > >> > > >> > > > scriptName=C:\somewhere\royale-asjs/mustella/tests/mxtests/basicTests/spark/scripts/ButtonTestScript.mxml > > >> id=SparkButtonTest1 result=pass elapsed=1463 phase=body > > >> started=1639654508820 extraInfo= msg= > > >> [java] 1639654510294 Marionette INFO Stopped > > >> listening on port 62311 > > >> [java] > > >> [java] ###!!! [Parent][RunMessage] Error: Channel closing: too > late > > >> to send/recv, messages will be lost > > >> [java] > > >> > > >> BUILD SUCCESSFUL > > >> Total time: 32 seconds > > >> > > >> But you sure there's nothing earlier that failed on yours? > > >> > > >> > > >> On 12/17/2021 1:50 AM, Greg Dove wrote: > > >> > Thanks again Edward, that was certainly much easier than last time I > > >> set up > > >> > for this (which was quite some time ago and required downgrading to > an > > >> > older version of Firefox etc). > > >> > > > >> > However, do you know if it is normal for all tests to pass and then > > see > > >> > this at the end in js?: > > >> > > > >> > [java] RESULT: > > >> > > > >> > > > scriptName=C:\development\asf\royale-asjs/mustella/tests/mxtests/basicTests/spark/scripts/ButtonTestScript.mxml > > >> > id=SparkButtonTest1 result=pass elapsed=1438 phase=body > > >> > started=1639727175704 extraInfo= msg= > > >> > [java] 1639727177157 Marionette INFO Stopped > > >> listening > > >> > on port 53835 > > >> > [java] > > >> > [java] ###!!! [Child][RunMessage] Error: Channel closing: too > > late > > >> to > > >> > send/recv, messages will be lost > > >> > [java] > > >> > [java] > > >> > [java] ###!!! [Child][MessageChannel::SendAndWait] Error: > Channel > > >> > error: cannot send/recv > > >> > [java] > > >> > > > >> > BUILD FAILED > > >> > C:\development\asf\royale-asjs\build.xml:1577: Java returned: 1 > > >> > > > >> > > > >> > thanks, > > >> > Greg > > >> > > > >> > On Thu, Dec 16, 2021 at 4:26 PM Greg Dove wrote: > > >> > > > >> >> Thanks Edward, I will keep that in mind for the future. Meanwhile I > > >> made > > >> >> changes today that got it to pass. > > >> >> > > >> >> > > >> >> On Thu, Dec 16, 2021 at 4:21 PM Edward Stangler > > >> >> wrote: > > >> >> > > >> >>> If you have Windows and Firefox installed, then just download and > > >> >>> extract geckodriver-v0.30.0-win64.zip: > > >> >>> > > >> >>> https://github.com/mozilla/geckodriver/releases > > >> >>> > > >> >>> and do this (in your build+test environment): > > >> >>> > > >> >>> set GECKODRIVER_HOME=c:\geckodriver-v0.30.0-win64\geckodriver.exe > > >> >>> ant mxtests-run-js > > >> >>> > > >> >>> (ant basictest-run-js passes) > > >> >>> > > >> >>> Buried in the output is: > > >> >>> > > >> >>> TypeError: panelView.contentArea is undefined > > >> >>> > > >> >>> > > >> >>> > > >> >>> On 12/15/2021 2:03 PM, Greg Dove wrote: > > >> >>>> I will have to come back to that, it is something I consider to > be > > >> not > > >> >>> an > > >> >>>> easy setup, so need to figure it out. > > >> >>>> > > >> >>>> > > >> >>>> On Thu, Dec 16, 2021 at 8:48 AM Greg Dove wrote: > > >> >>>> > > >> >>>>> Ok, so I just did > > >> >>>>> ant runmxtests > > >> >>>>> and it ran the swf tests, they passed. > > >> >>>>> So it looks like this is failing in js tests. I need to figure > out > > >> how > > >> >>> to > > >> >>>>> run those... > > >> >>> > > >> > > >> > > >
