Who Browsers Are For
The most pivitol tool a web developer uses day in and day out is a browser. They are what we develop for. Browsers can equally enstill excitement and dread throughout a project. As a web developer, it can be hard to maintain perspective of the purpose of browser—to meet the needs of the typical user.
Browsers are justsoftware and there are bound to be bugs and issues. Thankfully most browser makers have instituted short release timeframes to take care of minor bugs quickly. But even so, the browser makers’ priority is a feature rich experience for the user. These are features that aren’t associated to any standards, but instead provide the user with preferencial features. One of the reasons I prefer to use Safari has my main browser is the built-in feed reader and tabs syncing. Other browsers offer these features as well, but I like how Safari does it.
Browsers aren’t primarily made for developers, but they are a vital community to a browsers survival. At that web developers are completely reliant on the existance of state of browsers to accomplish their job. We need to maintain constant dialogue between web developers and browser makers.
Here is where you can log a bug for each major browser maker:
Follow The Browsers
Additionally consider following the Twitter accounts, blogs, and mailing lists of all the browsers to be aware of what they are up to. WebKit has a great blog, Chromium has a very active community forum, and Opera is quite intent on tweeting all kinds of things.
Make The Web Better Through Engagement
Take the time to document and report a bug, and make the web better.