As web developers, we all approach our work very differently. And even when you take a look at yourself, you’ll notice that the way you do your work does vary all the time. I, for example, have not reported a single bug to a browser vendor in the past year, despite having stumbled over a couple. I was just too lazy to write them up, report them, write a test case and care about follow-up comments.
This week, however, when integrating the Internationalization API for dates and times, I noticed a couple of inconsistencies and specification violations in several browsers, and I reported them. It took me one hour, but now browser vendors can at least fix these bugs. Today, I filed two new issues, because I’ve become more aware again of things that work in one browser but not in others. I think it’s important to change the way we work from time to time. It’s as easy as caring more about the issues we face and reporting them back.The post Web Development Reading List #172: On Reporting Bugs, DNS Subdomain Takeovers, And Sustainable UX appeared first on Smashing Magazine.
Source: Smashing Magazine
Web Development Reading List #172: On Reporting Bugs, DNS Subdomain Takeovers, And Sustainable UX