Google Chrome is more useful than Mozilla Firefox

I negate. I posit that Firefox is better than Chrome for several reasons. First, according to my opponent's PCMag.com source, Firefox defeated Chrome in graphics hardware acceleration. PCMag.com notes, "The next frontier in browser performance is about graphics hardware acceleration. In this area, Internet Explorer and Firefox are ahead of Google Chrome, Opera, and Safari. Microsoft was the first browser maker to make an issue of hardware acceleration in the buildup to its releasing IE9. The company's site for its browser, called IETestdrive.com, sports a slew of demonstrations that show off hardware acceleration, which you can try running in any browser. On these, you can clearly see IE and Firefox's lead in hardware acceleration." (Source: http://www.pcmag.com...). Next, PC Mag conducted a series of tests and noted that Firefox defeated Chrome in four out of the seven categories, including Psychadelic Browsing, which tested rapid color change and animation handling, and a Hardware Acceleration Stress Test. This is directly from his own source; you can check it yourself. Moreover, Firefox is better for testing because it offers an HTML viewing mode and thus is used by web developers when testing their website. "When the code of our sites has bugs, often it generates HTML code that is incorrect or even invalid. So we need to examine the HTML code to help figuring what is wrong. Firefox has this awesome feature that lets you select a portion of a page and it shows the exact HTML that corresponds to selected page portion. There is no such feature in Chrome. The best you have is an Inspect Element feature that lets you find the HTML code for the page element under your mouse pointer. It is not the same thing. If I selected a region of the page, I would like to view the whole region HTML, not just a single element. Another annoyance is that Chrome tries to beautify the HTML code. This means that if you have malformed HTML, you will not see where it is malformed, as Chrome will show you a beautified version of the HTML code after have been already fixed. I wish there was an option to disable beautification." Source: http://www.phpclasses.org... In addition, Chrome is more difficult to use than Firefox; doing simple tasks like shutting off Javascript require lengthy processes that are inconvenient. The same source notes, "Sometimes you need to test your site with JavaScript disabled. The only way to disable it in Chrome is going to preferences and disable it there. This is a real drag. In Firefox you can use the Web Developer extension by Chris Pederick to add a button to the browser toolbar to quickly disable and re-enable JavaScript any time you want. For Chrome there is also the Web Developer extension by the same developer but it does not provide a means to disable JavaScript. The problem is due to a limitation of the Chrome API exposed to extensions. It does not provide a way to disable JavaScript from extensions. There is a feature request for the Chromium project to implement the necessary support to disable JavaScript. The feature implementation was even assigned about 1 year ago to be implemented, but it never happened. Oddly users were disallowed to post further comments to that feature request." Moreover, Chrome is riddled with bugs that cause it to crash when it ought to be handling normal, easy project. The same source contends, "The Flash extension crashes frequently I do not develop sites in Flash. However, sometimes I need to access certain Google sites that provide useful information presented using Flash. That is the case of Google Analytics and Google Webmaster Tools. Unfortunately, the Flash extension shipped with Chrome crashes frequently. That does not happen when using Firefox to access the exact same pages." In addition, Mozilla welcomes and begs for user input, while Google Chrome does not allow for reporting of bugs. The same source notes, "10. No feedback to bug reports I tried to report some of the problems above using Chrome built-in bug reporting system. You go on the menu Tools and then Report an Issue, and it shows a nice bug report page which may even include a screenshot of the current page you were browsing. The problem is that I never got any feedback of my bug reports. So I do not know if the bugs were submitted and received properly, let alone having been seen and acted upon. I do know if the time I spent trying to describe the bug reports was worth it. I suspect that it would probably be more efficient if I reported any bugs to the Chromium project directly. Maybe I am getting this wrong, but sometimes I get the feeling that Google people does not see the act of providing feedback to the user community as an important thing." Even more devastatingly, Chrome does not display XML Documents properly even though XML documents are important in web development. "Chrome doesn't display XML documents nearly as well as Firefox Firefox uses a default stylesheet whenever it encounters an XML document. Here's an example (the server info document from the Wowza streaming server): Chrome, on the other hand, treats XML as HTML and does a horrible job displaying it... Firefox's rendering of the XML document is great - very readable and usable. In contrast, Chrome's rendering of XML awful." (Source: http://www.slicksurface.com...). In addition, Firefox is just as fast as Chrome; Firefox 8 eliminates many of Firefox's 7's problems and is thus just as fast as Chrome is. (Source: http://www.extremetech.com...). Responses to Opposition Contention1 is based on the Peacekeeper browser test. Unfortuantely, this test may be biased beacuse it relies on internet users to subject their browsers to the test. Perhaps Chrome users have better, faster computers because they are more likely to be "techy", thus causing an inherent bias in the testing. In addition, the Peacekeeper test amalgamates the older versions of the broswer with the newer version's results, so the output they produce is biased and does not account for updates. Contention 2 is completely wrong; he never even bothered to discuss the majority of the tests in his source. His source actually concludes that Firefox is better than Chrome, so you can turn this against him and vote for the negative. Contention 3 is basically irrelevant because Firefox offers the same features. Firefox is open source freeware, so many users help develop plug-ins and apps to improve Firefox and promote customization. In fact, Firefox's user-base and plugins are better developed than Chrome because they have attracted users for a greater period of time. Again, this is a reason to vote negative. Vote negative and for the browser that currently holds over 50% of the market.