Black (#000000) doesn't work with browser theme / dark mode

Half question / half hack. I found a bug (I think) with libraries and browser theme. When trying to save color variables in my library for backgrounds and shadows, certain colors were not being respected by the browser theme. This seems to only apply to pure black (#000000).

For example, I had a “background” color that I wanted to be white in light mode and black in dark mode, but in dark mode it showed as white. Same for shadows with transparency; I wanted to use 20% black in light mode and 100% black in dark mode, but it showed as 20% no matter what.

For now, my ‘hack’ was to use colors slightly different than black (like #010101), which did the trick. Has anyone else had issues with this? Am I doing something wrong? Maybe it’s more of a browser-related quirk I don’t know about?

Hey @narr8or :slight_smile:
Would you have a video showing how you setup and bound your colors? It seems like I can set a pure black

Thank you for checking into it @jptrinh — I went back and tried again (the exact same way). It’s working. No clue why it wasn’t, maybe needed a refresh?? :melting_face:

Anyway, glad that’s not a bug after all! And have to say, I’m loving WeWeb (and its community) the more I get into it. Coming from Webflow then Bubble, I finally get all the best parts of both and get to leave the bad parts behind.

1 Like

Love to hear that!
What are the best parts for you? :slight_smile: I also come from Webflow, so I’d guess the design freedom?

It’s a bunch of things. I loved the design freedom of Webflow and the interface they made to edit it. WeWeb built on this and improved the way styles are stored and edited, so that every edit you make doesn’t have to affect a class like in Webflow (Finsweet developed a whole template and strategy for working with it to make up for that shortcoming).

Bubble is great for adding logic and data options to a website design, but the interface is painful, and design options are limited. Plus, as we’ve used it more we find the drawbacks of a system that tries to do front and back end — both suffer greatly and improvements come slowly.

WeWeb is proving to check all the right boxes, doing front end really well and integrating seamlessly with awesome backends like Supabase and Xano. I think the only big hangup from switching fully to a WeWeb+Supabase stack is branch control, which seems to be in the works on both sides.

1 Like