René

the real origin was that back in the days playwright did actually keep a handle on the real element. similar to Selenium. BUT you may know the problems with Seleniums...

the `*` selection does not work with the cascading selectors! that is independent if you get the guid or not, because this guid thing was still just resolved to a...

So this Playwright code: ```typescript await page.locator('*css=.box >> "ABS"').locator('input')._selector ``` gives the following selector: ``` *css=.box >> "ABS" >> input ``` So it will not be the `input` element that...

And i think the overall problem here is, that you have an element that is not visible and therefore Get Bounding Box does fail with this error. I can without...

Get BoundingBox does fail with weird error: ``` async function getBoundingBox(request2, state2) { const selector = request2.getSelector(); const strictMode = request2.getStrict(); const locator = await findLocator(state2, selector, strictMode, void 0,...

i would not like to return `None`. If you call `Get BoundingBox` you normally expect a dictionary or number and not None. i am fine adding an additional argument that...

playwright states that null is returned if hidden. element not found would be an error that we won’t suppress. if you return an empty dict, users may access the `x`...

i do agree that this is a regression. before we did anything with the result, it would have worked. we do not have the policy to behave same as Playwright....

@robinmackaij Playwright itself is imho not really consistent. Examples: - `inputValue` throws if the selected element is not an `input`, `textarea` or `select` - `isChecked` throws if the element is...

I would not want to do a new keyword actually. I would just allow the file path to be a list or a dictionary or list of dictionary. This is...