After UI update, class='Vibrant Success' button is blue instead of green. How can I make the button green again?

It looks like the same color is being used for both Success and Primary classes

I�m guessing that's a bug. I will report it.

Vibrant Success has been adjusted by the update to also display as a blue in line with the branding. However it is still possible to display a button in green (or another color with the hex code for it). You can do so using the formula below:

"<a class='Vibrant Success' style='border:1px solid #6BBD57; background-color:#6BBD57'>Vibrant Success</a>" 

That one above will now show the button in green and if you adjust the hex color it will update to the button to the corresponding color.

That's ridiculous. The class is supposed to define the formatting, including the color. To have the work around is great, but you now have two classes that have the same format. That's a dev 101 no no

Hey All,
Our initial thought was to change all of Vibrant Success, including the Save and New Record buttons, to be blue. We received feedback from customers tested with that in many cases they have text on their forms literally saying "Click the big green button to save this record". So, we preserved the green for those two instances, but shifted to the blue color scheme for the rest. 

Personally, I think it's an issue if you need to spell out the color of the save button to get people to click it, but for this release we didn't want to alter functionality at all, only change styling, so this is the compromise we arrived at.


Sam Jones
QuickBase Product Manager
 

Sam,

My cheat notes to myself are that if you paste this formula into a formula rich text field, you get all the known easy colours.  (ie before I knew that we could actually specify a colour

List("&nbsp;",
    "<a class='Vibrant'>Vibrant</a>", // regular grey button
    "<a class='Vibrant Alert'>Vibrant Alert</a>", // yellowish
    "<a class='Vibrant Danger'>Vibrant Danger</a>",  // red
    "<a class='Vibrant Primary'>Vibrant Primary</a>", // blue
    "<a class='Vibrant Snowy'>Vibrant Snowy</a>",  // white
    "<a class='Vibrant Success'>Vibrant Success</a>" // green
)

So I just made the field again in a test app, and all the buttons continue to work except that the Vibrant Success turned Blue like the Vibrant Primary.

I read your post above a couple of times, but I'm still not understanding why you felt OK to retain all those other colours (which I appreciate), but not the Green.  Given that it arguably takes coding to specifically choose a button colour (ie a basic day to day admin should not know that formula, only coders or keeners who use this forum), why would that be changed?

Was it that the designers felt that purple and green do not mix well?  But now we are sort off off the purple for any custom headers, so does that argument still hold on Day 2 of the New UI?

>It was a push to reduce the number of colors we're using

But is clashes with commonplace UX design principles. Green hints at PROCEED and SUCCESS actions while Blue hints at DEFAULT or PRIMARY actions.

Both Bootstrap and Zurb use similar color schemes for their buttons.

Twitter Bootstrap Buttons
https://v4-alpha.getbootstrap.com/components/buttons/#examples

Zurb Foundation Buttons
https://foundation.zurb.com/sites/docs/v/5.5.3/components/buttons.html#button-colors

In any event I am no fan of conventions. QuickBase should have more affordances to customize styles through partials. A partial is a small fragment of  HTML that can carry its own style and content and possibly substitute data into the HTML through a template of some sort. So instead of the interface asking for a single branding color which is hard-coded into the page the interface should asks for a partial - a fragment of HTML that can include styles, images, text content etc.

Users want partials not purple.

I agree with Dan.  We would like our Green back please without me needing to survey all my clients to ask if they have any buttons which are now blue which they seem to recall used to be green.  I would not bother doing that so that they will just stay blue unless someone complains.  But that is a very nuanced thing to notice that inconsistency.

Spread the word, people:

https://quickbase.uservoice.com/forums/111823-quick-base-product-feedback/suggestions/33039928-bring...

Thx Blake for taking the time to make that post,
I voted my max 3 votes.