I've tried to use to DomCrawler as web scraper, but find it somewhat confusing and unintuitive. I believe this might just as well be me misunderstanding it's intended use.
Anyway, is the DomCrawler mostly intended for functional testing, or is it meant to be more full fledged "web browser" (or web page reader). I especially find it hard to extract either the whole document or the html/xml-representation of a node. I believe it would be quite easy to add this functionality (and I would be happy to do it), but I wonder if this within the intended scope of the DomCrawler Component. The README.md and docs<http://symfony.com/doc/current/components/dom_crawler.html> suggests that the DomCrawler is kind of jQuery for PHP. However, it currently lacks of lot functionality to achieve this goal. I would be happy to take a look and add functionality to make it more powerful. PS.: As someone who does not follow all the discussions and commits (or barely any), I find it hard to find out the intention behind certain components, and what's the roadmap/planned/wanted feature set of each. Is the dev-mailing list the place to go for this kind of info? -- 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
