-
Notifications
You must be signed in to change notification settings - Fork 295
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
info windows in settings not properly displayed. #965
Comments
klslz
changed the title
info windows in settings properly displayed.
info windows in settings not properly displayed.
Dec 21, 2023
Could you please provide a screenshot showing the issue with a page other than Material? |
Nice try. ;) Last time I looked the most, if not all, other advanced setting sheets are configured with info fields not that close to the border. Probably the reason why I hit the issue with MaterialSkin. |
It's not a "nice try". I'm only asking for more information to better understand what your issue is about. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LMS version: Latest git - default LMS theme
While working with the Material Skin plugin preferences in the standard LMS UI an issue popped up.
There are two prefs at the very bottom of that Settings/Advanced/Material Skin page.
These come with an I (info) option and are located quite close to the browser border.
Now.
When opening the related info screens in the Chrome browser, the info windows open towards the bottom.
The popups are larger than the remaining space towards the bottom.
The LMS config simply cuts them off at the bowser border. Depending of the remaining space the window
contents are partially and sometimes not at all displayed.
Scrolling the browser window further down is not possible, since the actual sheet size gets
not dynamically adjusted when the popups open.
The issue was confirmed on different browsers and OSes. over at the slimdevices forum.
The issue was also reported at Material Skin. MS considered it a LMS issue.
The text was updated successfully, but these errors were encountered: