Alex Rudenko
Alex Rudenko
@Holo-xy I wonder if using locale overrides https://www.w3.org/TR/webdriver-bidi/#command-emulation-setLocaleOverride works around this issue? I imagine if you the locale is fixed, there could be no need for additional normalization?
cc @sadym-chromium
cc @natorion
Coordinate based clicking currently is known to not perform so well with the models but I think we can support it as an option.
I had to read the documentation till the end before posting. It looks like I should extend the tokens list to add the support for nesting selectors.
I found that there is an example under Extensibility section: https://parsel.verou.me/?selector=%23foo+%3E+.bar+%2B+div.k1.k2+%5Bid%3D%27baz%27%5D%3Ahello%282%29%3Anot%28%3Awhere%28%23yolo%29%29%3A%3Abefore#:~:text=in%20the%20console!-,Extensibility,-You%20can%20import but if it could be supported out of the box, it'd be great.
cc @sadym-chromium
@sadym-chromium could you please take a look?
Can you achieve the desired outcome by calling https://w3c.github.io/webdriver/#perform-actions with pointer actions https://w3c.github.io/webdriver/#pointer-input-source?
Sorry, what I meant is that if the ChromeDriver correctly emits touch events if you the perform-actions API. Reading the click spec it seems like in the step 8 the...