Jeff Croft

I’m a product designer in Seattle, WA. I recently worked at Simply Measured, and previously co-founded Lendle.

Some of my past clients include Facebook, Microsoft, Yahoo, and the University of Washington.

I’ve authored two books on web and interactive design and spoken at dozens of conferences around the world.

I’m currently accepting contract work and considering full-time opportunities.

Filter content

Items tagged browsers

  • Blog entry // 01.09.2014 // 12:08 PM // 1 Comment

    Someone called Mike gets it. Except he doesn’t.

    Someone going by the name “Mike” responded to my recent post Web Standards Killed the HTML Star, but he did so on Jeffrey Zeldman’s follow up post. It was an amusing comment, because he simultaneously laughed at me for being so wrong and perfectly made my point for me. He said:

    An interesting read. However, I completely and utterly disagree. When you say “80% of what made us useful was the way we knew all the quirks and intricacies of the browsers. Guess what? Those are all gone. And if they’re not, they will be in the very near future.” I laughed heartily to myself. 80% of the time I take to complete a web project is usually taken up with browser testing — with older versions of IE being the main culprits.

  • Blog entry // 09.30.2008 // 4:39 PM // 82 Comments

    When can we stop talking about “supporting” certain browsers?

    Even at a progressive, Web Standards-friendly agency like Blue Flavor, the topic of which browsers to “support” comes up. Clients ask us, “Will our site be supported by IE6?,” for example. And even in the Web Standards community, there’s still a lot of talk about “dropping support” for IE6, and the like.

    But doesn’t this whole idea of browser “support” kind of go against what Web Standards is all about in the first place? Because of the way we build sites (and by we, I mean me, Blue Flavor, and most readers of this site), our projects inherently “support” every browser, from Lynx to Mosaic 1.0 to Netscape to IE to Safari to the no-name browser on your crappy flip phone.

    And yet, we still talk about browser “support.” What we really mean when we ask if a site will “support,” say, IE6, is “will the site look the same in IE6 as it does in the latest and greatest browser?” But we all know this is a silly question. Of course it won’t. And what’s more, it shouldn’t.

By content type
Other tags in these items