Incomplete code was pushed in a browser build not ready to come out

Jul 10, 2012 11:32 GMT  ·  By

Last week, Maxthon was threatened to be blacklisted from Niels Leenheer’s HTML5 test page because he discovered the browser enabled HTML5 features that did not work.

As much as everybody thinks of this deal as an unfair way for Maxthon to promote itself as the browser with most support for HTML5, the “misconduct” seems to have at the root plain, human error.

In an apologetic blogpost yesterday, the Chinese company revealed that at fault was incomplete code implemented in a browser build that was not supposed to be pushed out.

So there you have it: poor QA process that did not work flawlessly and which will be remedied with another layer of QA review being implemented, as Karl Mattson, GM Maxthon International, told us.

Furthermore, the development departments are currently at work fixing up the code, with the end of the week as the deadline for the task.