![]() ![]() Currently that means Camino, Flock, iCab, Netscape, OmniWeb, Opera, SeaMonkey, Shiira, WebKit Nightly, and any other newcomers. When something major (a full page template or a particularly tricky part of a design) is done I give it a quick check in the latest version of every browser that runs natively on Mac OS X. It’s always running anyway, so it only takes me a couple of seconds to check that everything is still ok, which it almost always is. Safari, being my browser of choice for non-development stuff, is next. Firefox, Mac OS Xįirefox is not my favourite browser for “casual” browsing, but when developing a website, especially if I’m doing JavaScript work, nothing beats it. It has turned out to work well for me, but it won’t work for you unless you’re a Mac user: 1. Ok, enough of that, here is my personal browser testing order. Sure, there are plenty of shops that still have that mindset, but it feels really backwards. To me it felt like everybody (well, mostly project managers and Microsoft-oriented developers) was looking for reasons to exclude this browser or that browser, this group of users or that group of users. When you look back a few years browser market share was always very important in every project. The only time we do mention specifics is when a client asks for a detailed list of supported browsers, and that has happend only once or twice in the last several years. ![]() Instead we mention the standards browsers need to understand in order to handle full functionality and design, and explain that the content will be accessible regardless of which browser the visitor uses. Doing that seems like a thing of the past to me. I’ve never taken the time to document my testing process, so this was a good opportunity to get it done.įirst of all, at NetRelations we rarely mention specific browsers to clients. My testing order, why I test in the browsers I do, and why I do it in that particular order. After reading Andy Clarke’s article CSS: Browser testing order I’ve been thinking a bit about my own approach to testing CSS and JavaScript during development. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |