- From: Andreas Tolfsen <ato@mozilla.com>
- Date: Thu, 5 Mar 2015 09:30:01 +0100
- To: public-browser-tools-testing <public-browser-tools-testing@w3.org>
On 25 Feb 2015, at 23:53, Seva Lo <vlotoshnikov@gmail.com> wrote: > My point was that if this new feature is added to the standard and some implementations actually implement it, then many other implementations still won't, for a while. Then the feature won't see much use from those who care about portability of their code across browsers. That is true, but this is an example of something we can add without any form of backwards-incompatible concerns. > The feature is maybe nice, but it is too easy for me as a user to avoid using it for the sake of portability of my code, and I would be avoiding using it until most drivers I know implement it - which will not happen for a while even it is in the standard. If you target W3C WebDriver compatible remotes and Selenium WebDriver remotes restricting yourself to the intersection of what can reasonably be supported by both seems like a good idea.
Received on Thursday, 5 March 2015 08:30:33 UTC