You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The http protocol fetched the address and gets 200:OK but the section is not there anymore...
now... I know this is how HTTP/browsers work - but is there a way to catch those use cases?
The text was updated successfully, but these errors were encountered:
The difficulty is to know what to test. For some pages the # anchor is in the HTML directly but for others it's compiled from some JS and requires the page to be rendered. Does having the basic case of looking for the anchor in html source code enough for you or do you absolutely need to look deeper and render the page as if it was displayed on a browser?
For example, my
README.md
file contains the following link:The
http
protocol fetched the address and gets200:OK
but the section is not there anymore...now... I know this is how HTTP/browsers work - but is there a way to catch those use cases?
The text was updated successfully, but these errors were encountered: