Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DomCrawler] fix HTML5 parser integration#31257
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
stof commentedApr 26, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I don't understand which issue you are trying to solve here. We cannot add content multiple time (as all nodes have to belong to the same document), and calling |
Uh oh!
There was an error while loading.Please reload this page.
nicolas-grekas commentedMay 5, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The code makes little sense either: one should not have to know how the overall class works to understand local details. I'm making the code have a better locality so one can reason about it in a simpler way. |
This PR was merged into the 4.3 branch.Discussion----------[DomCrawler] fix HTML5 parser integration| Q | A| ------------- | ---| Branch? | master| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -Spotted while reviewing#30892The current logic is context-dependent: by changing the order of calls, you can get different behaviors.Commits-------ba83bda [DomCrawler] fix HTML5 parser integration
Spotted while reviewing#30892
The current logic is context-dependent: by changing the order of calls, you can get different behaviors.