Michał Lipok

It looks like some frames are blocked:  

After testing with FireFox the one thing what comes to my mind that Chrome gives us much more information. Because FireFox returns only `#39 frames` and Chrome `#145 frames` 

I think It is possible. I think that it depends on cookies and geolocation diferences in both browsers.

ok so currently get another issue with: https://github.com/Danp2/au3WebDriver/blob/42dda7d9a9e78b3c7cc2d419b0e84eaf1335f6a8/wd_demo.au3#L942-L948 here is my modification: ```autoit ; entering to the frame _WD_DebugSwitch($_WD_DEBUG_Full) _WD_FrameEnter($sSession, $sFrame) If @error Then Return SetError(@error, @extended, '') ClipPut(_WD_GetSource($sSession)) MsgBox($MB_TOPMOST,...

this following part ```autoit ; entering to the frame _WD_DebugSwitch($_WD_DEBUG_Full) _WD_FrameEnter($sSession, $sFrame) If @error Then Return SetError(@error, @extended, '') ClipPut(_WD_GetSource($sSession)) MsgBox($MB_TOPMOST, "", 111) ;~ $aFrameList = _WD_FrameList($sSession, True, 0,100) ;~...

> until you scroll into view `#frame_advanced_select_with_multiple_features` and `'//*[@name="pets"]` is there something wrong with: `_WD_WaitElement($sSession, $_WD_LOCATOR_ByXPath, '//*[@name="pets"]')` I mean `_WD_WaitElement` by defulat should not care about element visibilty: ```autoit If...

> > Because FireFox returns only #39 frames and Chrome #145 frames > > I wonder if that's a function of the website where it renders the page differently based...

Today I'm little tired. Going rest. Will back tomorrow.

hm... it means that I should suplement `_WD_FrameList` accordingly

> A few thoughts / suggestions -- > > * Maybe you could make it optional? Otherwise, the webpage would be forced to unnecessarily scroll to each frame. that was...