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
Hi there. We noticed that the output generated is producing a %2f encoded value instead of a /. That's not a problem for a browser but it can be a problem for any tool looking for validity of references. In our case, it can't validate the page because it thinks it misses the links.
Yeah, I think you can consider a minor issue as it does not affect directly the user experience. However I wonder why this %2f is only present in the Packages section and the rest of html document is using normal / in the hrefs.
argh my memory doesn't serve me as to why we added urlencode. technically you can have id with / and hrefs to that as urlencoded version of it. (see recent PRs/commits) the links should still work?
Hi there. We noticed that the output generated is producing a
%2f
encoded value instead of a/
. That's not a problem for a browser but it can be a problem for any tool looking for validity of references. In our case, it can't validate the page because it thinks it misses the links.An easy workaround we're using is to replace the encoded value, so, the check is not failing anymore.
The text was updated successfully, but these errors were encountered: