On Browser Testing
Published on Apr 10, 2012 (updated Feb 5, 2024), filed under development. (Share this post, e.g. on Mastodon or on Bluesky.)
This and 133 other posts are also available as a well-behaved ebook: On Web Development.
The primary goal for cross-browser testing is to make sure that documents are usable and consistent across different user agents and devices. Even if you understand this to include both functionality and design, the definition of “usable” is interesting.
Three ideas look particularly important when attempting a definition:
A document should look as intended in all major user agents and devices, yet shouldn’t apply excessive force towards pixel perfection.
A document should be fully functional in all major user agents and devices, yet make smart use of graceful degradation.
A document should be operable within acceptable user and user agent boundaries, acknowledge that there are user preferences and device constraints outside of a developer’s control, and deem a certain degree of user engagement to be reasonable, like (vertical) scrolling, zooming, and rotating.
I’d like to probe these statements—please share your thoughts.
About Me
I’m Jens (long: Jens Oliver Meiert), and I’m an engineering lead, guerrilla philosopher, and indie publisher. I’ve worked as a technical lead and engineering manager for companies you use every day (like Google) and companies you’ve never heard of, I’m an occasional contributor to web standards (like HTML, CSS, WCAG), and I write and review books for O’Reilly and Frontend Dogma.
I love trying things, not only in web development and engineering management, but also with respect to politics and philosophy. Here on meiert.com I talk about some of my experiences and perspectives. (Please share feedback: Interpret charitably, but do be critical.)
