V6B2 | Minor Issues

  1. Noticed that trying to edit the title of something by double clicking on the name from the outline landmark it doesn’t actually save your changes. Once you hit enter it reverts back to “Untitled

Screen Shot 2022-10-12 at 9.13.47 AM Screen Shot 2022-10-12 at 9.13.51 AM

  1. Workflow is a bit odd when the elements tab preserves your search. Can’t tell you how many times I’ve added an element like a button, done a bit of configuring or designing, gone back to add a text element and done this:

  1. For copy / pasting of styles, you used to be able to click on an entire row containing multiple headlines throughout multiple columns and apply headline styles to all headlines in that container. Now it looks like I have to click the specific element and apply styles one at a time.

  2. Transparency of global color not rendering properly on the frontend. This is an icon with a background to transparency set to 0.1. First image is how it looks in the builder preview. Second image is how it looks live.

Working on a build right now so might add to this if any other minor things show up.

Thanks for writing in, @DoncoMarketing!


#1. Noted. This is working on pages it seems, but needs to be finalized in other instances for the same behavior. Apologies on that!


#2. Agreed. I have made a note and this will be changed so that search results are cleared out whe navigating away from a Workspace.


#3. I believe Misho noted this as well and I have a line-item in for it to be addressed.


#4. Noted, this will be fixed.

1 Like

@DoncoMarketing, so I looked into #4 a bit more and it looks like we’ve got an issue tracking for this already in our systems. Basically, if you’re using a color for a global value and plan on using the alpha slider later with it, hex values do not currently work with the way the parser registers this. However, if you switch your color to an rgba value, it should start working. The actual fix for this will likely take some time as it will require updating both the color parser and / or the regex statements we’re using to address all of these contexts appropriately, and I’m not entirely sure if we’ll get to it within the bounds of this cycle. But try switching out your values to rgba and see if that works for you…I tested it locally and can confirm things are working as expected on my end in both the live preview and the frontend.

All other items mentioned here have been fixed and will be in for the next beta.

Thanks!

1 Like

@kory- All makes sense. Personally, can work around the hex / rgba issue no problem. That said, can see this causing a bunch of unnecessary headache for users. Perhaps some inclusion in global colors docs until fixed.

You sir are appreciated. Thanks!

@DoncoMarketing, will definitely be making a note for this in the docs until it can be cleaned up. Thanks!

1 Like