I currently have a page that needs to be scrolled down to fully load the elements I'm trying to scrape.
When I run my scraping code locally, it scrolls fine and successfully loads all the elements.
Snapshot after local run where all elements are successfully loaded:
Current Behavior
However, when I run this in lambda the scrolling does not work.
The elements are not totally loaded (50 elements that are loaded in the beginning vs the 400+ that get loaded in when I run it locally.
I've tried using different selectors as targets to scroll to but none seem to work.
Snapshot after lambda run after scrolling is called:
Environment
chrome-aws-lambda
Version: chrome-aws-lambda:22puppeteer
/puppeteer-core
Version: 21.5.2Expected Behavior
I currently have a page that needs to be scrolled down to fully load the elements I'm trying to scrape. When I run my scraping code locally, it scrolls fine and successfully loads all the elements.
Snapshot after local run where all elements are successfully loaded:![1701686880746-elementCount_424](https://github.com/alixaxel/chrome-aws-lambda/assets/64991505/04ac3695-e045-49f1-923b-4376df127192)
Current Behavior
However, when I run this in lambda the scrolling does not work. The elements are not totally loaded (50 elements that are loaded in the beginning vs the 400+ that get loaded in when I run it locally. I've tried using different selectors as targets to scroll to but none seem to work.
Snapshot after lambda run after scrolling is called:![1701688595177-elementCount_50](https://github.com/alixaxel/chrome-aws-lambda/assets/64991505/4c6e7bab-3c7d-4075-ad9c-7c2735cb81cb)
Steps to Reproduce
URL: https://sports.bwin.pt/pt/sports/futebol-4/apostar
Has anyone experienced this?