Re: [webappsec-testsuite] runner.js puzzler

So, it seems a cross-browser workaround is to:

Send the report to a php script that writes it to disk.
Then load a script...
 Using "defer"...
   To create and append a hidden iframe...
      That calls a another php script...
         That reads the report off disk...
            and postMessages it to the parent window...
               Which performs tests on the data in the main document
context.

/need a beer now

Still would like any hints on how to put tests in grandchildren iframes of
runner.js without breaking it, if you know how.

-Brad


On Wed, Jun 26, 2013 at 2:43 PM, Brad Hill <hillbrad@gmail.com> wrote:

> So, I've made some fixes to reporting to accommodate Firefox not accepting
> cookies on CSP reports, but now I'm noticing something else strange: It's
> only running half the tests.
>
> After a bit of debugging, it seems that runner.js is using completion
> callbacks from testharness.js to advance through the manifest.  The CSP
> cases all have an sub-iframe for checking the report, and callbacks are
> bubbling up from that and causing the runner to advance prematurely, so
> every other test gets skipped. (at least that's what I think is happening)
>
> But only in Firefox!  ¯\(°_o)/¯
>
> Anyone have any ideas?
>
> -Brad
>