You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am seeing an issue where a logo that is displayed as a background for an tag is not being captured by wraith. I assume it is some kind of phantomjs issue. I have set a 10 second delay in the before capture call to no avail. When I hit the site directly the page render is almost instant. It seems that phantom doesn't render out the tags background image so it can't be captured. That is my guess anyway. Hopefully someone can shine a light on this one.
Please let me know if you need any more info.
The text was updated successfully, but these errors were encountered:
Which version of Phantom are you using? And what is the CSS being applied to the tag?
PhantomJS (and particularly older versions of PhantomJS) uses quite an old rendering engine that doesn't necessarily support modern browser features (so if this is an SVG or base-64 encoded background image, for instance, Phantom might fail to render it).
Some of my colleagues prefer SlimerJS because it seems to be better at rendering more modern CSS, but Wraith does not support it out of the box (feel free to +1 issue #364 if you'd like to request that we provided dedicated support for it).
As of v3.2.0, Wraith now works with newer versions of Phantom and Casper - try updating to the latest versions of these and see if that solves your issue. Thanks
I am seeing an issue where a logo that is displayed as a background for an tag is not being captured by wraith. I assume it is some kind of phantomjs issue. I have set a 10 second delay in the before capture call to no avail. When I hit the site directly the page render is almost instant. It seems that phantom doesn't render out the tags background image so it can't be captured. That is my guess anyway. Hopefully someone can shine a light on this one.
Please let me know if you need any more info.
The text was updated successfully, but these errors were encountered: