The committers listed above are authorized under a signed CLA.

• ✅ login: Chris8711 (ce78dad, b2bfe47)

I can observe that selenium python lib already has a wrapper for active element:

class SwitchTo:
    def __init__(self, driver):
        import weakref
        self._driver = weakref.proxy(driver)

    @property
    def active_element(self) -> WebElement:
        """
        Returns the element with focus, or BODY if nothing has focus.

        :Usage:
            ::

                element = driver.switch_to.active_element
        """
        return self._driver.execute(Command.W3C_GET_ACTIVE_ELEMENT)['value']

Wouldn't this be a duplicate then?

I can observe that selenium python lib already has a wrapper for active element:

class SwitchTo:
    def __init__(self, driver):
        import weakref
        self._driver = weakref.proxy(driver)

    @property
    def active_element(self) -> WebElement:
        """
        Returns the element with focus, or BODY if nothing has focus.

        :Usage:
            ::

                element = driver.switch_to.active_element
        """
        return self._driver.execute(Command.W3C_GET_ACTIVE_ELEMENT)['value']

Wouldn't this be a duplicate then?

yes. I haven't noticed that.
Thank you

this is duplicated

Btw, sending keys to an active element is now W3C's send_keys action.
appium/appium#16419 (comment)

Get an active element -> calling send_keys to the element is also the same, but the w3c action's one is old send_keys_active_element ([:post, 'session/:session_id/keys']) endpoint alternative in W3C