-
-
Benachrichtigungen
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors after upgrading from 4.3.0 to 4.3.1 #171
Kommentare
So I traced this to tool tips. When capybara pulls up a page during a test to examine it and a Bootstrap tool tip exists, it fires this off in the log. The test passes; however, does anyone know what might be causing this or how to better trace what is going on? I am not using any HTML in the tool tip that the new sanitizer might affect. It is just text. |
I am able to avoid these errors being logged if I bypass the sanitizer like so:
Not what I want to do of course, but at least this narrows it down more. |
I doubt this has anything to do with the rubygem in particular. Consider posting your issue upstream. |
Note I had the same exact issue and it was really a problem with PhantomJS... we will consider alternative headless javascript runners |
I upgraded this gem from 4.3.0 to 4.3.1. Now when running my tests I am getting errors logged such as:
These errors happen when running rspec using capybara and during a
visit
command to visit a page.All the tests seem to be passing, but I am trying to figure out what is causing these errors being logged to the console as the tests are running.
The text was updated successfully, but these errors were encountered: