Priyansh Garg

@Terence625 In that case, you could use `await` with `element.find` and `element.findAll` commands. Awaiting these commands returns a `WebElement` which can be directly used with other commands. ```ts import {...

You're right. I think we should be doing both of these things: * Allow to pass `ScopedElement` to older commands (this could be done by checking if a `.webElement` property...

Sure, @yashPratp983! Go ahead.

Hey, this project is not a priority as of now so we won't be taking contributions for it.

I tried to run npm init on a Windows 11 machine with Chrome 115 and Node 18.16 and the setup is working fine, not able to reproduce this issue. Seems...

@kretschmannj Can you help me with the command you were using to maximize the window and are you still facing this issue?

There are a few commands here that I'm not sure with: - `.element()` (This command is still being used in backwards compatibility mode, so need to check once if moving...

@itsspriyansh You can check Nightwatch's new element API documentation [around here](https://nightwatchjs.org/api/element/clear.html). Each `elementId...` command can be replaced by a corresponding command in the new element API. For other commands, if...

@reallymello Do you still face any such issues? I think Example 2 in the issue description was fixed later on (I'm not sure when) because we don't get boxes now...

Although not entirely the same issue but I faced a similar issue while working with https://github.com/reallymello/nightwatchTutorials/tree/master/pomTypescriptExample3.4.1  To reproduce, setup the project linked above, make a copy of `nightwatch/tests/google.ts` file...