Scrollbar makes left splitter disappear in Chrome on Windows

[StefanBattmer]

Hi there,

we recently migrated our documentation to your awesome project. I stumbled on a small issue however which I hope is not related to #86. I think it is not since we are using Doxygen 1.9.6 but maybe it is. Anyway on Windows when using Chrome (Firefox is working fine) once enough items are expanded on the left side so that a scrollbar is activated the splitter seems to be under the scrollbar and as a result you can no longer move it. Please see attached screenshot. The live version of the documentation can be found here: https://www.matrix-vision.com/manuals/SDK_CPP/index.html

This somehow seems to be related to the webkit definition for Chrome in the CSS. If you disable that the splitter works so maybe there is indeed a connection to #86. I will be happy to provide more information when needed.

[jothepro]

Oh, I think I never tested for that scenario. 😨
It seems to be broken on Windows only, but it's also really hard to grab the splitter on Linux and macOS.
Thx for reporting this bug! I don't think it's related to #86.

As a sidenote: @r0ckarong has posted an interesting approach to improve the UX regarding the sidebar resizing. Maybe that would be an interesting approach to fix the problem.

[StefanBattmer]

@jothepro: Thanks for the feedback! Just to make sure this has been said: This project is indeed awesome! I really like the look and feel that it generates!

I noticed one more issue that I think is related. Some tables in that setup (e.g. when they are wide enough to require a scrollbar) do not display borders on the left an right side of the table as well:

This can be seen here: https://www.matrix-vision.com/manuals/SDK_PYTHON/DeviceApiSupport.html.

An example without scrollbar can be found here: https://www.matrix-vision.com/manuals/SDK_PYTHON/ImageProcessing.html

[StefanBattmer]

I just noticed, that my last comment probably duplicates #91. So this already seems to be addressed.

[jothepro]

Jup, that is very likely. I hope to be able to address this issue asap.

[jothepro]

This should be fixed in the new release v2.2.0.

Pls reopen the issue if the fix doesn't work for you.

[StefanBattmer]

Just checked with our documentation. Works like a charm! Thanks! @jothepro: You might wanna update the year in your license file to something like Copyright (c) 2021 - 2023 jothepro

[jothepro]

Ouh, thx for the hint! I missed out on that!