Skip to content

fix(css-loader): ensure CSS loader uses loading patch for PhantomJS 1.9#280

Merged
ocombe merged 1 commit intoocombe:masterfrom
booleanbetrayal:fix_phantom19_readystate
Feb 2, 2016
Merged

fix(css-loader): ensure CSS loader uses loading patch for PhantomJS 1.9#280
ocombe merged 1 commit intoocombe:masterfrom
booleanbetrayal:fix_phantom19_readystate

Conversation

@booleanbetrayal
Copy link
Contributor

Hey @ocombe - Noticed today while trying to get PhantomCSS (which relies on Phantom 1.9.x) setup for our single page app, that the CSS loader promises never completed. Seems like Phantom 1.9.x is also subject to the same readystatechange / event loading issues that other WebKit variants suffer from. This fixes that!

@booleanbetrayal booleanbetrayal force-pushed the fix_phantom19_readystate branch from e393504 to 54d68e9 Compare February 2, 2016 03:42
@booleanbetrayal
Copy link
Contributor Author

Had a stale fork. I just rebased against upstream master to fix a conflict.

@ocombe
Copy link
Owner

ocombe commented Feb 2, 2016

Good catch, thanks :)

ocombe added a commit that referenced this pull request Feb 2, 2016
fix(css-loader): ensure CSS loader uses loading patch for PhantomJS 1.9
@ocombe ocombe merged commit 50bd3c8 into ocombe:master Feb 2, 2016
@ocombe
Copy link
Owner

ocombe commented Feb 3, 2017

I just released 1.1.0 with this, I think I did it right, I haven't published a new version on this repo for ages, let me know if it works

@booleanbetrayal
Copy link
Contributor Author

👍

@booleanbetrayal booleanbetrayal deleted the fix_phantom19_readystate branch February 3, 2017 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants