E-mail List Archives
Re: Automated testing tools and viewport size
From: Patrick H. Lauke
Date: May 6, 2020 1:00PM
- Next message: glen walker: "2.4.7 or 2.1.1 on "hidden" submenu elements?"
- Previous message: Steve Green: "Re: Automated testing tools and viewport size"
- Next message in Thread: Jared Smith: "Re: Automated testing tools and viewport size"
- Previous message in Thread: Steve Green: "Re: Automated testing tools and viewport size"
- View all messages in this Thread
On 06/05/2020 18:43, Steve Green wrote:
> I never really thought about this before, but automated testing tools that use a headless browser still need to apply viewport dimensions, and this will determine which media queries are and are not applied. This raises the question of what dimensions they are using.
Yes, ideally, the tool should really run at every major breakpoint
defined in CSS, and possibly some further random samplings/common device
widths/heights. And orientations/aspect ratios.
I pointed this out a few years ago as well for tools like the Trace
Center Photosensitive Epilepsy Analysis Tool (PEAT) (which, last time I
checked, assumed/required a browser at 1024x768 in order to do its
calculations of screen area). Those tools will, essentially, only
capture one single potential state, and if they can't be modified to
work at different viewport sizes, their results will be potentially
meaningless.
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
- Next message: glen walker: "2.4.7 or 2.1.1 on "hidden" submenu elements?"
- Previous message: Steve Green: "Re: Automated testing tools and viewport size"
- Next message in Thread: Jared Smith: "Re: Automated testing tools and viewport size"
- Previous message in Thread: Steve Green: "Re: Automated testing tools and viewport size"
- View all messages in this Thread