Replies: 1 comment 3 replies
-
Original plan was yesterday, unfortunately I've had some water ingress into our garage so I've had to deal with that as a priority. New packages should be available within the hour. Workaround incase you need a fix sooner is pretty straight forward //Replace
chromiumWebBrowser.ExecuteScriptAsync(method, args);
//With
chromiumWebBrowser.GetBrowser().ExecuteScriptAsync(method, args); |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We've run into the recursion issue that was recently fixed.
Since we want to use this in production ASAP (and currently can't because I updated the NuGet package too early and thus now have the version with the issue in my application), my question is:
Is there any timeline estimation when this fix will be available as a new NuGet package?
Beta Was this translation helpful? Give feedback.
All reactions