Casino game wiki display messed up in fullscreen, any ideas?

It seems to me that your wiki’s responsive design is broken. Problems displaying in full screen typically mean that media queries are not handled correctly, or that the size of a container has been forced to a certain number of pixels. Look for viewport units (vw/vh) or percentage used incorrectly in place of pixels. Then check your flex/grid box elements, as they may be inheriting the wrong size from parents. Try testing with various browser zooming options: some people have scaling set in their operating systems by default. If your audience is mostly mobile, make sure you don’t have any desktop hacks that interfere with resizing. To isolate the problem, try forcing the mobile view. Check your CSS for max-widths that will truncate content on wider views. Confirm that you don’t have any competing @media queries at common breakpoints. Sometimes third-party CSS from templates, such as a casino theme, can cause conflicts. Confirm the behavior in other browsers and on other devices. If you’d like me to help track down the bug, let me know!

Might be responsiveness issue. Check on other devices and in other browsers, also mobile. Try Lighthouse performance test. Could it be that your css media query is not covering full screen?? Is your main container div having proper max width and not set to full width ?? Are there any absolutely positioned elements in the way ??? I can help to debug it!

Have you tried the website’s responsive design setting? It might not display properly when viewed in full screen. I’d suggest testing for conflicting CSS media queries. Have the impacted customers try different browsers and operating systems. Browser zoom options may affect the site as well. Check for any third-party widgets or advertisements that could be affecting how the site renders. You need to keep things simple! Is there anything else you want to discuss?

Check your CSS media queries - they may not be designed for fullscreen mode. Test on a mobile device, as that’s likely similar. See if the behavior changes when you use browser dev tools (F12). Could it be a plug-in causing issues? Disable them and test. I can continue helping you troubleshoot if you’d like!