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 +0000, 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-14 21:38:20 +0000, Anne van Kesteren said:
I don't think we should actively recommend it. We're maintaining the
existing code, but are not upgrading our level of support or anything.
And if we could get rid of the existing code, we would.
Well, there's the expected yes/no answer I was looking for. My
inclination is to go ahead and migrate the doc and keep it in the main
body of our documentation content, but maybe with an added notice that
support is limited yadda yadda yadda...
Any disagreements?
FWIW, many add-ons use XPath. If there's anything we should be
recommending add-on developers to migrate to, please let me know.
Jorge
With Reminderfox add-on (FX, TB and SM) we use XPath to aggregate and
output calendar listing. That's a very flexible method and can be edited
without XPI code change. Loosing XPath would disable Printing/Viewing of
calendar details.
Which alternatives?
Guenter
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
