Platforms-supported.md

@@ -2,9 +2,7 @@
 
 ## Overview
 
-The combination of Selenium 1 and Webdriver APIs should provide the testing
-support below. See the next sections for details specific to each browser and
-possible limitations.
+The Webdriver API (with the help of the legacy Selenium 1 API) provides the testing support below. See the next sections for details specific to each browser and possible limitations.
 
   * MathJax outputs:
     * HTML-CSS using STIX, TeX or ImageTeX fonts.
@@ -24,53 +22,35 @@ possible limitations.
 
 ## Firefox
 
-Automated testing works with Firefox on Linux, Windows and Mac using Webdriver.
-
-It is currently the fastest driver, the most convenient to use and it requires
-no specific configurations or workarounds.
+Automated testing works with Firefox on Linux, Windows and Mac using Webdriver. It is currently the fastest driver, the most convenient to use and it requires no specific configurations or workarounds.
 
 For details, see [http://code.google.com/p/selenium/wiki/FirefoxDriver](http://code.google.com/p/selenium/wiki/FirefoxDriver).
 
 ## Opera
 
-Automated testing works with Opera on Linux, Windows and Mac using Webdriver.
+Automated testing works with Opera on Linux, Windows and Mac using Webdriver. It is one of the fastest driver, one of the most convenient to use and requires no specific configurations or workarounds.
 
 Note that MathJax support for STIX fonts is disabled for that browser, so you
-can only use TeX fonts. On Windows, use Opera >= 11.60 to avoid issues with the
-program files directory being unwritable. Otherwise it is one of the fastest
-driver and one of the most convenient to use.
+can only use TeX fonts.
 
 For details, see [http://code.google.com/p/selenium/wiki/OperaDriver](http://code.google.com/p/selenium/wiki/OperaDriver)
 and [https://github.com/operasoftware/operadriver#readme](https://github.com/operasoftware/operadriver#readme).
 
 ## Chrome
 
-Automated testing works with Chrome on Linux, Windows and Mac, using Webdriver.
-
-However, the Chrome driver on Linux has a serious limitation at the moment:
-[it is not possible to take screenshots](http://code.google.com/p/chromium/issues/detail?id=89777#c4).
-Hence, when you execute a set of tests that includes visual reftests, you must
-use the Selenium 1 API instead, which seems two to three times slower that the
-Webdriver API. Otherwise, the speed should be comparable to Firefox or Opera.
-
-An additional configuration is required to use the Webdriver API: you must
-install the [ChromeDriver server](http://code.google.com/p/chromium/downloads/list)
-on each test machine.
+Automated testing works with Chrome on Linux, Windows and Mac, using Webdriver. The speed should be comparable to the Firefox and Opera driver. You must install the [ChromeDriver server](http://code.google.com/p/chromedriver/downloads/list) on each test machine.
 
 For details, see [http://code.google.com/p/selenium/wiki/ChromeDriver](http://code.google.com/p/selenium/wiki/ChromeDriver).
 
 ## Internet Explorer
 
-Automated testing works with Internet Explorer on Windows, using Webdriver.
+Automated testing works with Internet Explorer on Windows, using Webdriver. Compared to other drivers, the execution of the tests is very slow. You must install the [Internet Explorer server](http://code.google.com/p/selenium/downloads/list) on each test machine. Other configurations may be necessary because of some Internet Explorer's security restrictions.
 
 The selection of the document mode is currently implemented using the Selenium 1
 API and Java keyboard events. This is not really reliable but is the best we
 can do until 
 [issue 2564](http://code.google.com/p/selenium/issues/detail?id=2564)
-is fixed. Several instances can be executed on the same machine at the same time (TODO: do not allow simultaneous Init phase, to prevent some conflicts during document mode selection).
-
-To use Webdriver, you may need to do some
-[specific configurations](http://code.google.com/p/selenium/wiki/InternetExplorerDriver#Required_Configuration).
+is fixed. If you execute several instances on the same machine, be careful that they do not start simultaneously for otherwise there may be conflicts between the keyboard events during the selection of the document mode.
 
 For details, see [http://code.google.com/p/selenium/wiki/InternetExplorerDriver](http://code.google.com/p/selenium/wiki/InternetExplorerDriver).