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
Similar to #7799 most Adafruit libraries have a jquery error that makes the bottom left panel non-working in the RTD docs. It seems that new libraries from the past weeks are not affected (I added a library to RTD last week without the issue).
As mentioned in that PR: it seems that jquery gets "loaded/injected" into the page after the page finishes loading, so it doesn't work when it's used the first time in the page. The fix forces jquery to be included earlier in the page. I looked at adding it to the cookiecutter, but the issue doesn't seem to affect new repositories so it's more a question of fixing old libraries.
My understanding is that there are maybe hidden version pinnings in RTD for its static files or modules that can't be updated from the user side. I don't know if that's the issue and how to fix it if it is. Maybe the above patch is a simpler solution.
Weird issue, lots of maybes.
The text was updated successfully, but these errors were encountered:
Similar to #7799 most Adafruit libraries have a jquery error that makes the bottom left panel non-working in the RTD docs. It seems that new libraries from the past weeks are not affected (I added a library to RTD last week without the issue).
As mentioned in that PR: it seems that jquery gets "loaded/injected" into the page after the page finishes loading, so it doesn't work when it's used the first time in the page. The fix forces jquery to be included earlier in the page. I looked at adding it to the cookiecutter, but the issue doesn't seem to affect new repositories so it's more a question of fixing old libraries.
My understanding is that there are maybe hidden version pinnings in RTD for its static files or modules that can't be updated from the user side. I don't know if that's the issue and how to fix it if it is. Maybe the above patch is a simpler solution.
Weird issue, lots of maybes.
The text was updated successfully, but these errors were encountered: