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
We're having a lot of questions about JavaScript, and one rather frustrating aspect of MechanicalSoup is that users may start using it, write a lot of code, and then realize that they need JavaScript for a tiny bit of code. Then the suggestion to use Selenium probably sounds like a betrayal to users, because they have to rewrite all their code.
I'm not suggesting that we should write our own JavaScript interpreter, but implementing a Selenium back-end for MechanicalSoup may actually be rather easy to do. The benefit for completely new users compared to using Selenium directly is probably weak, but this could offer a nice migration path for users who need to migrate from MechanicalSoup to Selenium.
The text was updated successfully, but these errors were encountered:
We're having a lot of questions about JavaScript, and one rather frustrating aspect of MechanicalSoup is that users may start using it, write a lot of code, and then realize that they need JavaScript for a tiny bit of code. Then the suggestion to use Selenium probably sounds like a betrayal to users, because they have to rewrite all their code.
I'm not suggesting that we should write our own JavaScript interpreter, but implementing a Selenium back-end for MechanicalSoup may actually be rather easy to do. The benefit for completely new users compared to using Selenium directly is probably weak, but this could offer a nice migration path for users who need to migrate from MechanicalSoup to Selenium.
The text was updated successfully, but these errors were encountered: