We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Via @rsc, who encountered the following broken escaping on pkgsite:
Repro steps:
The text was updated successfully, but these errors were encountered:
Interestingly, the test appears to look for this escaping explicitly: https://cs.opensource.google/go/x/pkgsite/+/master:internal/frontend/fetchserver/fetch_test.go;l=170;drc=ebe617b30c52774fccf9d36331cbff31e99aaf9e
Sorry, something went wrong.
Hmm, I don't know if/how this ever worked. Perhaps @jba recalls?
fetch.ts uses new DOMParser().parseFromString(...), but that doesn't unescape:
fetch.ts
new DOMParser().parseFromString(...)
I guess this was fixed just by updating the pkgsite backend... last week.
No branches or pull requests
Via @rsc, who encountered the following broken escaping on pkgsite:
Repro steps:
The text was updated successfully, but these errors were encountered: