On Wed, May 16, 2012 at 7:49 AM, Paul Davis <[email protected]> wrote:
> Oh, I missed the scoping a bit on that. Should be for browsers, but
> for the CLI tests I wouldn't be surprised if that fails with a "no
> property named EventSource on undefined" or whatever. I'd just add a
> if(window && window.EventSource) to fix if that's the case.
>
> Though we should add a ticket to revisit this since we're
> theoretically moving to the CLI tests, no point having test code that
> never runs and all that.
>

It should be better on latest change witch take the undefined bit in
consideration. CLI tests pass here.

- benoit

Reply via email to