I’m assuming it’s a new user error but my Googling hasn’t uncovered what that might be (kind of hard with “unresponsive responsive” type language lol)
Also: I checked and these buttons are working on other pages I built myself but aren’t functional for reusable elements I recently built. I’m guessing there’s a reason that Bubble just isn’t telling me.
Props to @bcart0v for finding the n00b error I was making. Wish they’d include a tooltip when those views are disabled for this reason! Thanks for the quick and easy solve.
Related question to check my understanding of the responsive engine’s capabilities: it seems like I basically have to build break points for everything (as opposed to using a tool like Squarespace where responsive breakpoints are basically built in). I’m building out a site from a mobile-first view to include wider widths. Is the best practice here to have a page set to column layouts then use fixed width groups combined with other layouts to get the layout I want at wider widths?
Fixed widths (in my experience) can get a little messy, as they don’t really auto-move around (unless you tell it to) when the page width has changed.
But yes, in general I use Columns as my “base” and then throw in some rows when needed, and you can add conditionals to change the sizing or padding or alignment based on screen size. It is a tad tedious at first, but once you get the hang of it, you can run right through it.
I’ve exclusively used column layouts since I’ve been building for mobile. I’ve been real willy nilly with using margins and sometimes padding to adjust things. I’m assuming now would be the time to commit to columns/rows and elements with consistent padding and using margins + conditionals to build out device sizes? I’ve been dreading that process so I appreciate your encouragement!
