Comment 8 for bug 1667208

While I'm happy to see this fix released, I'm not so happy that it broke all of our company's Selenium-based scripts running on Ubuntu 16.04 by making a non-backwards-compatible change in an LTS release. All of our scripts had been written to accommodate the "buggy" behavior that has been present since Xenial's release by specifying the ChromeDriver path at '/usr/lib/chromium-browser/chromedriver'. Now, after applying the latest security updates, these scripts are finding that their ChromeDriver has gone missing.

In order to provide backwards-compatibility on the LTS releases, could you please provide (in a packaging update) a symlink at the old '/usr/lib/chromium-browser/chromedriver' location pointing to the new '/usr/bin/chromedriver' location?

Thanks for your consideration of this request.