yeah

Hey, so I have the following test that is failing for PhantomJS and Nashorn, but works fine for Safari, Firefox, Chrome, and SlimerJS:

(ns debug.promise-test
  (:require [cljs.test :refer-macros [is testing async deftest]])
  (:import [goog Promise]))

(deftest promise-test
  (testing "Can pull a value out of a Promise"
    (async done
      (-> (new Promise (fn [resolve] (resolve 1)))
        (.then (fn [val]
                 (is (= 1 val))
                 (done)))))))

AFAIK PhantomJS does not have js/Promise, does goog.Promise polyfill it?

Yeah, that's the idea

I came at this bug playing with polyfills, but I'm giving you guys the minimal thing to reproduce the problem

The only reason for bothering with Promises is because I'm trying to wrap crypto.subtle, which handles everything in Promises. I want to fall-back to synchronous JS implementations and a polyfilled Promise-facade if that API isn't available.

It's probably a bug in goog.Promise - maybe the right thing to do is to drop it and use core.async channels?

@xcthulhu I would try to test it with another polyfill implementation, for example taylorhakes/promise-polyfill worked for me

under phantomJS

Okay, I'll give it a shot. Thanks a tonne!