-
-
Notifications
You must be signed in to change notification settings - Fork 381
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
Some nodes are lost #487
Comments
Hello @wpyok500 , You are comparing HAP with the HTML rendered (so after some javascript has been run). If you check the source code, you will see the node also have no value: <em>
<span title="无持续风向" class="NNW"></span>
<span title="无持续风向" class="NNW"></span>
</em> See the following answer to have more information about this kind of issue: #482 (comment)
Best Regards, Jon Sponsorship Performance Libraries Runtime Evaluation |
@JonathanMagnan
exists when HtmlDocument.LoadHtml() is used, and the
tag is lost after using SelectNodes .
|
HtmlAgilityPack does not simply lose the content of the <i> nodes when using SelectNodes. Proof: https://dotnetfiddle.net/rtBnoM Note the If you somehow still see the problem with SelectNodes, double-check and make sure you are using the most current HtmlAgilityPack version. |
Hello @wpyok500 , Sorry, you are indeed right, the text is part of the source code, I checked the wrong part of the source. However, @elgonzo is also right; in the latest version, no bug seems to exist. Here is another Fiddle copied from the one from @elgonzo that also do the Best Regards, Jon |
@elgonzo @JonathanMagnan hello I found that there is a problem of losing the i tag when using 1.11.46. After rolling back 1.11.45, the i tag will not be lost. After upgrading to 1.11.46 again, there is no such problem. |
Here is what to include in your request to make sure we implement a solution as quickly as possible.
1. Description
Some nodes are lost
2. Exception
url: http://www.weather.com.cn/weather/101230203.shtml
3. Fiddle or Project
If you are able,
Provide a Fiddle that reproduce the issue: https://dotnetfiddle.net/25Vjsn
Or provide a project/solution that we can run to reproduce the issue.
Otherwise, make sure to include as much information as possible to help our team to reproduce the issue.
4. Any further technical details
Add any relevant detail can help us, such as:
net472
The text was updated successfully, but these errors were encountered: