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
Disclaimer: This is not a bug in wysihtml5 per se, but it took me some time to track it down and it is in place in the code with some "hack" comments.
Bug: if you open a page with wysihtml5 in Selenium (tested with Firefox and Selenium 2.39.0), it crashes the test with
6:08:42.377 WARN - Exception thrown
java.lang.IllegalArgumentException: Required attributes are not set or any non-null attribute set to null
at org.openqa.selenium.Cookie.validate(Cookie.java:140)
at org.openqa.selenium.Cookie.<init>(Cookie.java:86)
at org.openqa.selenium.Cookie$Builder.build(Cookie.java:225)
at org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions.getCookies(RemoteWebDriver.java:665)
at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringOptions.getCookies(EventFiringWebDriver.java:519)
at org.openqa.selenium.remote.server.handler.GetAllCookies.call(GetAllCookies.java:33)
at org.openqa.selenium.remote.server.handler.GetAllCookies.call(GetAllCookies.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:170)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
16:08:42.377 WARN - Exception: Required attributes are not set or any non-null attribute set to null
This can be fixed by commenting this line (this._unset):
// This doesn't work in Safari 5
// See http://stackoverflow.com/questions/992461/is-it-possible-to-override-document-cookie-in-webkit
this._unset(iframeDocument, "cookie", "", true);
It seems to me that this line is not necessary (looking at it and the comments above this code), but someone who understands wysihtml better should take a look.
The text was updated successfully, but these errors were encountered:
Disclaimer: This is not a bug in wysihtml5 per se, but it took me some time to track it down and it is in place in the code with some "hack" comments.
Bug: if you open a page with wysihtml5 in Selenium (tested with Firefox and Selenium 2.39.0), it crashes the test with
This can be fixed by commenting this line (this._unset):
It seems to me that this line is not necessary (looking at it and the comments above this code), but someone who understands wysihtml better should take a look.
The text was updated successfully, but these errors were encountered: