← Back to context

Comment by gregpr07

4 days ago

Hi, the first version of Browser Use was actually built on Selenium but we quite quickly switched to Playwright

7 comments

gregpr07

Reply
hugs  4 days ago

yeah, i noticed that. apologies if i missed a post about it... what do you wish didn't suck about selenium?

  • moi2388  4 days ago

    Scrolling to an element doesn’t always work because somehow the element might not be ready. You need to add ids to the element and select by that to ensure it works properly.

    • hugs  4 days ago

      thanks! yeah, playwright was a huge improvement there -- waiting until an element was actually ready. the official posture from the selenium project ("figure it out, be explicit") wasn't always the most user friendly messaging.

      having to add ids to elements is one of those classic tradeoffs -- the alternative was to use css or xpath selectors, which can be even worse, maintenance-wise. i'm secretly hoping ai code-gen apps pumped out by things like Lovable or Claude Code automagically generate element test-ids and the tests for you and we never have to worry about it again.

      4 replies →