I think I know the answer to this, but want to confirm: is XPath a
going concern? We want to be sure of its current status before
migrating its documentation to where it ought to be assuming that it is
in fact something people still use.
--
Eric Shepherd
Developer Documentation Lead
Mozilla
Bl
On Mon, Apr 14, 2014 at 10:28 PM, Eric Shepherd wrote:
> I think I know the answer to this, but want to confirm: is XPath a going
> concern? We want to be sure of its current status before migrating its
> documentation to where it ought to be assuming that it is in fact something
> people still us
On 14/04/2014 22:28, Eric Shepherd wrote:
I think I know the answer to this, but want to confirm: is XPath a
going concern? We want to be sure of its current status before
migrating its documentation to where it ought to be assuming that it
is in fact something people still use.
XPath is stil
On 2014-04-14 21:38:24 +, David Burns said:
XPath is still a going concern from where I stand. Web Testing people,
who use Selenium WebDriver, use XPath extensively since they struggle
to get to have testable documents. Having decent documentation for them
would be awesome :)
On 2014-04-
Not from my side!
David
On 14/04/2014 22:41, Eric Shepherd wrote:
On 2014-04-14 21:38:24 +, David Burns said:
XPath is still a going concern from where I stand. Web Testing
people, who use Selenium WebDriver, use XPath extensively since they
struggle to get to have testable documents. Ha
On 4/14/14, 3:46 PM, David Burns wrote:
> Not from my side!
>
> David
>
> On 14/04/2014 22:41, Eric Shepherd wrote:
>> On 2014-04-14 21:38:24 +, David Burns said:
>>
>>> XPath is still a going concern from where I stand. Web Testing
>>> people, who use Selenium WebDriver, use XPath extensivel
On 14.04.2014 23:54, Jorge Villalobos wrote:
On 4/14/14, 3:46 PM, David Burns wrote:
Not from my side!
David
On 14/04/2014 22:41, Eric Shepherd wrote:
On 2014-04-14 21:38:24 +, David Burns said:
XPath is still a going concern from where I stand. Web Testing
people, who use Selenium WebD
On Mon, Apr 14, 2014 at 10:54 PM, Jorge Villalobos wrote:
> FWIW, many add-ons use XPath. If there's anything we should be
> recommending add-on developers to migrate to, please let me know.
It would be interesting to know what they use it for and why
querySelector() et al don't meet their needs,
On 15.04.2014 12:17, Anne van Kesteren wrote:
On Mon, Apr 14, 2014 at 10:54 PM, Jorge Villalobos wrote:
FWIW, many add-ons use XPath. If there's anything we should be
recommending add-on developers to migrate to, please let me know.
It would be interesting to know what they use it for and why
On 15/04/2014 11:17, Anne van Kesteren wrote:
On Mon, Apr 14, 2014 at 10:54 PM, Jorge Villalobos wrote:
FWIW, many add-ons use XPath. If there's anything we should be
recommending add-on developers to migrate to, please let me know.
It would be interesting to know what they use it for and why
On 15/04/2014 14:21, Andreas Tolfsen wrote:
On 15/04/2014 11:17, Anne van Kesteren wrote:
On Mon, Apr 14, 2014 at 10:54 PM, Jorge Villalobos
wrote:
FWIW, many add-ons use XPath. If there's anything we should be
recommending add-on developers to migrate to, please let me know.
It would be int
On 15/04/2014 14:33, Gijs Kruitbosch wrote:
On 15/04/2014 14:21, Andreas Tolfsen wrote:
On 15/04/2014 11:17, Anne van Kesteren wrote:
It would be interesting to know what they use it for and why
querySelector() et al don't meet their needs, but there's no immediate
threat of what we have going
12 matches
Mail list logo
