This repository has been archived by the owner on May 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Object.defineProperty behaves incorrectly in PhantomJS #11856
Comments
+1 Having this same issue |
Same issue here. |
Does it work correctly if you add |
@JamesMGreene Yes, if
|
This was referenced Sep 4, 2014
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
Apr 30, 2015
spalger
pushed a commit
to spalger/kibana
that referenced
this issue
May 1, 2015
san650
added a commit
to san650/ember-cli-page-object
that referenced
this issue
Jan 24, 2016
This commit workarounds an issue in phantomjs where we cannot use Object.defineProperty to redefine a property. See ariya/phantomjs#11856
FWIW, this bug is fixed in PhantomJS 2.1.1 |
Thanks! Closing this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The following behaves correctly in browsers and node.js, but incorrectly in PhantomJS:
Correct result:
PhantomJS result:
The text was updated successfully, but these errors were encountered: