Alex Rudenko
Alex Rudenko
I will probably not have time to look into this soon. I have made a fix in Chromium that should solve the previous issue and perhaps it solves this one...
The link gets multiple content boxes (because of the image) and Puppeteer takes the first context box as the baseline for the offsets . We need to see if there...
your code might not work if the link text wraps on the new line so depending on the exact text position you might click an empty space so bounding box...
@minggeorgelei there are no immediate plans on fixing that.
It looks like this has been fixed or at least I am not able to reproduce it anymore. What made the difference is the use of the getClientRects API to...
This is the behaviour of the headful mode and the new headless matches that behaviour. The old headless had a different behaviour here that does not match the actual Chrome's...
Looks like https://httpstat.us/401 is not available and I am not able to reproduce with the test server. Do you own the site? I wonder if other response parameters determine how...
Thanks for the repro. I am able to reproduce with http-server. I believe that some other headers and not only the 401 status code might be causing the issue.
Test "[click.spec] Page.click should click the button with fixed position inside an iframe" is flaky
This regressed in 22.11.0
Test "[click.spec] Page.click should click the button with fixed position inside an iframe" is flaky
Upstream https://crbug.com/358515466