We knew this was coming down the track, but the selenium project lacked the people to prevent it from happening. Sauce Labs donated Selenium Builder (nee Sauce

We knew this was coming down the track, but the selenium project lacked the people to prevent it from happening. Sauce Labs donated Selenium Builder (nee Sauce Builder) to the project to try and help. Applitools have recently leant some engineering muscle to the problem. The problem breaks down into two main areas: * Technical: the underpinnings have switched from the XPI model to Web Components. Mozilla are doing what they think is best for their browser, and I know that they make their choices with thought and data. * People: every successful OSS project has a company or person acting as its champion. The selenium project has people working flat out for the language bindings, the w3c "WebDriver" spec, grid, and supporting the community. We lack a champion with the time to spend on IDE. We can fix the technical side of things. The thing that we could really do help with is the people-side....