-
Notifications
You must be signed in to change notification settings - Fork 5
Version toggler and feedback dropdown look odd #497
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
Comments
@msbt figured the regression has been caused by sphinx-design-0.6.0, released just five days ago. Other than investigating about which kind of changes to CSS rules might have caused the regression, he suggested to downgrade to |
thanks @amotl, this seems to be the corresponding patch, where they change from chevron up/down to right/down: executablebooks/sphinx-design#192 |
Thanks. I can't spot the regression you outlined at https://cratedb.com/docs/crate/reference/ and friends. May I ask you to elaborate where it is visible? |
@amotl along those lines https://github.com/executablebooks/sphinx-design/pull/192/files#diff-aa63b0bb1f95ed68c20ca762bcff0c773ac1c9394680fbbe0f4c7417d41540b5L61-L80 this is where the chevrons change |
I totally accept and appreciate that you spotted an error. However, it is not visible for me in any way. Maybe you can support this case by referring to a spot where we can also see it? Within the OP, there is just a screenshot, but no reference to a corresponding spot. |
I am asking because a downgrade to a previous version of sphinx-design would be totally a no-brainer, like outlined at #497 (comment). However, because I can't spot any regression anywhere, I am doubting that it makes sense, because it will not make too much of a difference from my perspective. |
One thing to mention for anyone working on this, @msbt was able to patch this by injecting CSS with HubSpot - via fastly edge side includes, from what I understand. |
Ah I see. Now it totally makes sense that I can't spot any mistake, if it has already been fixed using a workaround. Thanks for clarifying. |
@amotl you can see the regression on any non-proxied url, e.g. So the padding changed and also the chevrons |
Now, everything makes sense. Thanks for clarifying. NB: Please don't use linkable URLs verbatim in public which can feed crawlers wrongly. |
Because sphinx-design 0.6 also trips software tests on sphinx-design-elements, and because I currently don't have the capacity to review and fix them, I am already downgrading on behalf of sphinx-design-elements, release pending. |
sphinx-design-elements v0.3.2 downgrades to sphinx-design v0.5, so the next downstream builds of crate-docs-theme should pick up corresponding package versions, effectively resolving this issue. Please verify, report back, and/or close this issue, all at your disposal. Thanks. |
|
It looks like it is fixed through the downgrading outlined above. |
I just found that in the changelog for sphinx-design 0.6:
|
We concluded the resolution of this flaw by adding relevant fixes and releasing crate-docs-theme 0.33.0. @msbt: Thanks for your support! |
@amotl apparently the docs are still being built with the old version ( |
Build #24863053 on "crash" says it uses |
@amotl that was back when the 0.33.0 wasn't on pyi |
@msbt reported a visual regression.
The text was updated successfully, but these errors were encountered: