`find_elements` sometimes can't find `<a>` nodes about chromiumoxide HOT 3 OPEN

Can reproduce this.
This seems to be an issue with how the newegg site triggers frame navigations.
I Could detect a lot of main frame navigations, after the correct one was already loaded (your url). The there are navigations to about:blank, https://newegginc.demdex.net/dest5.html?d_nsid=0#https%3A%2F%2Fwww.newegg.ca and various others, this seems to mess up the tracking of the main_frame in the frameManager which now doesn't track the your target anymore, but this is certainly strange. Could be a bug in how frames are reordered once navigated.
I need to debug this more thoroughly.

however, setting a manual delay seems to fix it for now std::thread::sleep(std::time::Duration::from_secs(3))

from chromiumoxide.

Ok thanks that’s an easy workaround. I’m super puzzled as to why buttons work haha

from chromiumoxide.

I tried it and it doesn't seem to work for me, even with 6s 😔

from chromiumoxide.