#Using NextUI + Mantine UI Libraries & Page Layout Issue

11 messages · Page 1 of 1 (latest)

teal rampart
#

Greetings! Since the first second I discovered NextUI through a Google search, I have been in awe of it. Before implementing NextUI for a better user interface, I was working on a project that I wanted to finish in time for its initial release.

However, I began using the Mantine component library before discovering NextUI, but I now want to use both of them since Mantine has more core functions and NextUI has a superior design. Therefore, I was wondering whether combining these two should result in any problems or just be okay.

Yet, ever since I installed NextUI and attempted to wrap my "_app" with NextUIProvider inside the MantineProvider, I've had a strange display when my app is launched. For a little moment, it will appear as though the CSS is broken before displaying the page content as intended. I mean, it still works in the end, but I still find it to be sort of meh given my need for the ideal experience. Eventually, I tried to unwrap my app and re-allow it to MantineProvider exclusively, but the issue has persisted ever since.

#

Here is a preview how how the page loads in the first place ⬆️

⬇️ And here is how it's supposed to load (which happens like 1s after page loads)

#

So after I stopped and restarted by app, the CSS issue appears to be solved, I guess this might be related to the CSSBaseline from the _document page? If so, Can NextUI work without it?

#

Yeah, it's def due to the _document css properties, thus wrapping my app inside NextUIPrivoder also gives me this annoying white bar on the top of the page

velvet lichen
#

For the baseline style, you can disable it by disableBaseline in NextUIProvider if you like

velvet lichen
teal rampart
velvet lichen
teal rampart