> And that'll have a lot more impact than testing cross browser regularly.
That depends entire on what you mean with "impact" here.
One site that does not work on Firefox has a great impact too. When that "one site" becomes every fourth site, then "we", the webdevelopers have handed Chrome their monopoly.
> That depends entire on what you mean with "impact" here.
Fair enough. I meant that using Firefox regularly as a web developer would have a larger impact on keeping the web free than testing periodically on Firefox. Why? Because testing periodically won't exercise the browser quirks as thoroughly as every day use (and sometimes time intensive cross browser testing gets sacrificed to schedule concerns). There's also an additional bonus of keeping browser share up, but that's not the primary benefit in my mind.
That depends entire on what you mean with "impact" here.
One site that does not work on Firefox has a great impact too. When that "one site" becomes every fourth site, then "we", the webdevelopers have handed Chrome their monopoly.