Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect nesting #17

Open
neverfox opened this issue Jul 10, 2016 · 0 comments
Open

Incorrect nesting #17

neverfox opened this issue Jul 10, 2016 · 0 comments

Comments

@neverfox
Copy link

neverfox commented Jul 10, 2016

In the wild, I have noticed that the results of parse-string don't always nest as expected. For example, if you pull in the DOM for https://www.google.com/search?q=dentist+pinellas+county+fl (I'm using clj-http to make the request), there is a div with id ires (the search results) that contains one child ol which itself contains 10 or so children with class g (each individual search result). The first of these children also contains class _Arj. However, the tagsoup result shows the ol and the _Arj g div as siblings, and the remaining g-classed divs as direct children of the body tag. I'm not sure if this is an issue with clj-tagsoup or something upstream, but I thought I'd bring it to your attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant