@timneutkens Wow, I like to hear that. 😃 Using nuqs always feels like a workaround, so nice to hear that this area of next will improve in the future. 😀
@colmtuite@emilkowalski@base_ui It really works out of the box with select, but not with combobox, because a combobox is not modal per default. My assumption was that those components behave the same. I just read bit about select vs combobox and understand that choice.
@colmtuite@emilkowalski@base_ui Yes, Base UI works the way if you open a select in a Dialog and then click somewhere IN the Dialog. But it would be nice if you could also klick outside the Dialog and then the select would close, instead of closing select AND Dialog.
@colmtuite@base_ui GridList, Listbox, Tree, ColorPicker, Calendar (currently i use react aria component primitives for that), compare-slider and zooming (currently i combine react-compare-slider and react-zoom-pan-pinch), react-overflow-list, react-resizable-panels, sidebar-primitives, ...
@infinterenders@sohamstwt "For a truly client-heavy app, the App Router needs to get "out of the way" once the initial page has landed." Yes, but at this point, next has not much to offer. 😒 Using nuqs can only partly compensate the missing first class client side navigation API.