I used the webpagetest.org with scripting where i was able to add setViewportSize (1920,1080) and i was able to capture bigger web page images for Chrome and Firefox, but when i ran the same script against my own AMI agent on EC2 the captured images sizes remain small/same as the default size.
can you tell me what i have to do on the AMI instance to capture bigger screen shots?
I think the desktop resolution might be set to 1024x768 on the EC2 AMI’s. I have a todo item to make that settable through the user data which would be necessary for larger screen shots. If you set it to a smaller viewport does it work?
Also, you’ll need the agent’s that came with the recently-released 2.7 release in your server’s work/update directory for the AMI’s to pick up the agent code with the right support.
is there anyway on the AMI instance i can change the default browser width/height used by modifying some configuration file? Because when i capture the screen shots on your test agent(Dulles:Firefox) i get bigger screen shots if i set the browser height/width via setViewportSize but not against the AMI instance.
The Dulles agents have a desktop resolution set to 1400x1050 (I believe). I configured them manually. The URLBlast code has some logic to make sure that the desktop is configured for at least 1024x768 and 24bpp and if not it will change it to that but the code is hard-coded right now. It’s not hard to change and I’ll try to get to it later this week.
Does setting a SMALLER viewport work? Just checking to make sure you have the correct agent code running and it’s just a desktop size issue. The agents pre-installed on the AMIs are pretty old so it will usually pull an update from your server.
Also having problems to set the view port size on EC2 AMI. (ami-8b2c2fff eu-west)
My script / testing on chrome (36):
setUserAgent Mozilla/5.0 (iPhone; CPU iPhone OS 7_0 like Mac OS X; en-us) AppleWebKit/537.51.1 (KHTML, like Gecko) Version/7.0 Mobile/11A465 Safari/9537.53
setViewportSize 320 568
The useragent string is recognized correctly (a mobile website is delivered) but the viewport size did not match…
Any news on this issue?