Ah, that's good news. Happens to me sometimes as well when trying to
translate C docs to Python :) Sometimes Python's help can be your friend
"help(WebKit.DOMDocument.evaluate)"
On Tue, Jul 2, 2013 at 5:12 PM, Niranjan Rao wrote:
> Simon,
>
> Thanks for the pointer. I noticed that I made a st
Simon,
Thanks for the pointer. I noticed that I made a stupid mistake and was
sending document as a first parameter.
Your example opened my eyes and now it looks like its running ok.
Thanks,
Niranjan
On 07/02/2013 02:37 PM, Simon Feltman wrote:
On Tue, Jul 2, 2013 at 10:35 AM, Niranjan Ra
On Tue, Jul 2, 2013 at 10:35 AM, Niranjan Rao wrote:
>
> And yes, I had tried creating empty WebKit.DOMXPathResult object and
> passing it. Did not work.
>
It would be helpful to know the details of what didn't work. Code examples
of what you have tried, or steps to reproduce the problems you are
Thanks for the information. I had came across the webkit bug you mentioned.
And yes, I had tried creating empty WebKit.DOMXPathResult object and
passing it. Did not work.
As much as I hate this, I see only following options for me now. As much
as I would have loved it, only python based solut
Hi,
On Mon, Jul 1, 2013 at 11:48 PM, Niranjan Rao wrote:
> I need to perform some DOM operations once the document is loaded. Webkit
> DOMDocument provides evaluate method which can allow me to reach to element
> using xpath, if it works. The parameter DOMXPathResult of the evaluate
> method ha
