This is how Bubble’s site looks like. Anything after is either similarly bad or worse. No point in using it in Explorer if I can’t know if the site I’m building will show up properly.
Bubble starts to become a joke. I literally cannot use it now.
I don’t use Opera, so can’t really comment on that (although it’s not on Bubble’s list of officially supported browsers)…
As for Chrome, what is your page layout type? (it looks like your page is not responsive)
Internet Explorer??? (does that still exsit)?.. in any case, Bubble doesn’t support Internet Explorer (it was officially retired by Microsoft earlier this year), so don’t expect your app to work correctly in Internet explorer… (it doesn’t support CSS Grid for one thing)…
Bubble starts to become a joke. I literally cannot use it now.
If you don’t like using Bubble, then don’t… find another tool that suits your needs better (if you can)…
Yes, I know. I understand that although that’s really annoying because the very websites that Bubble is supposed to build should work everywhere. It’s a site-building service for God’s sake. And Opera uses Chromium underbelly.
The problem emerged when I updated the Responsive for this page. And this is where from the screen is from. After posting I went back to using the old engine as it works. At least that works. At least in Chrome.
What do you do when a service doesn’t work on Chrome? I went to Explorer as the last resort.
I think I’ll need to move away from Bubble much quicker than I wanted. Sad, but come on, this is a series of huge bugs, not a one or two. Something seriously bad is hapening at Bubble.
P.S. If Opera, which is based on Chrome, is a joke here, then it may say more about Bubble (and community here?) more than anything else. Either case, it’s really saddening.
Yes, but have you actually made your page responsive? - i.e. by selecting a responsive layout type for the page?..
It looks to me from your screenshot that the page has a layout type of ‘Fixed’ (i.e. it’s NOT responsive)… the screen size buttons and grey slider aren’t supposed to work for a Fixed layout, so the behaviour is exactly as expected…
What do you do when a service doesn’t work on Chrome?
What service doesn’t work on Chrome?..
I think I’ll need to move away from Bubble much quicker than I wanted. Sad, but come on, this is a series of huge bugs, not a one or two. Something seriously bad is happening at Bubble.
What ‘huge bugs’ are you taking about?
The fact that Internet Explorer (an outdated and depreciated web browser) doesn’t support CSS Grid is neither a bug, nor does it have anything to do with Bubble…
The fact that you don’t know how to use the new Responsive Engine correctly is also not a bug…
So what exactly is the series of huge bugs you’re referring to?
The buttons don’t in any way show (for example by being light-gray) that they are not clickable. There is no comment to that. Remember that it’s not that nothing changes when I switch the width (for example by clicking on “992”), but it’s not clickable at all.
If what you say were true, that I somehow made an upgrade, but somehow didn’t upgrade some aspect of the upgrade, then this information did not show anywhere. And the buttons remainded unusable. In that case it would simply be a case of horrible UX.
As to bugs:
Obviously the behaviour of not being able to click buttons (or not informed as to why) and not working in Chromium-based browser are bugs. Either on the literal, or UX side. Either case, it’s really bad for Bubble.
I changed the layout away from “fixed” and the buttons started working. So it’s just a really bad UX where you cannot click things that are meant to be clicked