Hi, I recently started writing a webservice using Symfony2. After some development I started to write functional tests and therefore I came across the Crawler object and more specifically its filterXPath() method. It works just fine, but it took me a little to understand why my XPath queries were all failing: basically the method internally creates a DOMDocument object, appends a root element and then loop on the Crawler object itself to import all the needed nodes. The misleading behavior -I think, but perhaps there's a reason I can't clearly see at the moment- is to have a "_root" DOMElement forced in the internal DOMDocument as a root element. That would force the developer to either go for non-absolute paths(ie: "blog/posts" instead of "/blog/posts") -opportunity that might cause some problems in certain circumstances- or for a less clear, undocumented and implementation-dependent path(ie: "/_root/blog/posts").
I hope I made my point understandable enough :) Cheers and thanks for the great work -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
