Titus Fortner

It will still work. The deprecation notices are much more eager than we realized when we released.

This is more a major effort than something that belongs to a specific milestone

Ah, yes, for those, you'll need to construct your own `MutableCapabilities` instance. It's likely we'll eventually deprecate `DesiredCapabilities` from `RemoteWebDriver` like we did local driver classes, but will continue to...

Sorry for not following up on this. That's interesting that you're seeing it in multiple places. `Displayed()` kind of makes sense because it is a JS execution, I'm not sure...

As discussed in #10157 Something in `isDisplayed.js` atom is returning `false` and I'm not sure where to start with it.

So, the problem is with how Vue is messing with the DOM, and presumably users can update their code to avoid this issue. That said, this is probably a good...

Technically this is a bug in `vue-fragment` which removes ChildNodes from the container. `vue-frag` and Vue 3 both do this correctly. If Selenium changed the atom to use `parentElement` instead...

@GgStormer please change/update your library or raise an issue with vue-fragment. This is not a defect in Selenium. Additionally, the Selenium atom is not an easy thing to work with...

Looking at how we're doing this, I'm not sure we can remove this before removing the entire handshake code. I'm running the tests so we can see - https://github.com/SeleniumHQ/selenium/actions/runs/2799798464

@diemol when I'm suggesting we don't have good OSS tests to ensure handshake is working... I'm pretty sure this branch should have a bunch of failures, but everything is passing.