DUPLICATE: Editing on class level of an element doesn't show changes in builder, only when editing on ID level. Changes appear in frontend, not editor

Bugs
1

Browser: Tested in Chrome & Safari
OS: macOS
Video: https://share.d19.ca/f.php?h=11NXrVRF&p=1

I’m not sure if this was introduced in 1.8 or 1.8.1, but on 1.8.1 I’m seeing annoying behaviour recently when editing a class on an element (social icons for example) for typography for example, where changing the font-size doesn’t update the view in the editor, it only shows if I refresh the editor page. However if I change the typography on the ID level (it wasn’t set previously), it renders immediately in the editor.

Video taken to show the issue better too. Please review, and test ideally in the same way:

  1. Using 1.8.1, add the Social Icons / Icons List element to a page.
  2. Add a class to the element used in step 1.
  3. On the class, set the typography to any value, say “2 rem” for example.
  4. Save the page, refresh.
  5. Now re-do step 3 but use a different value of “0” or “1rem” for example, and notice there isn’t any change in the view. If you save though and look on the frontend you’ll see the change is made.
  6. Change the same setting but at the ID level and you’ll notice the editor successfully renders the changes in the builder/editor.

This affects the editor only but makes editing the builder very frustrating when making changes to elements typography for example. I tried looking for a post already but couldn’t find it, I apologize in advance if this is a duplicate.

2

We are aware of this bug and will provide a fix in the next update. It’s the same issue as reported in this ticket here WIP: Background color edits to classes not showing in editor - #5 by simon

1 Like
3

Ah that title is probably why I missed it - Thanks for linking it, @Thomas, I’m glad to know this is being addressed!

As I’m making a lot of edits to a staging site where I’m trying to do much of it on classes, I may need to roll back temporarily to an older release as the impact of this defect is quite large to the editing experience.

Honestly a bit surprised this one wasn’t caught in testing, hopefully this is a test-case that’ll be added in the future. If there’s anything I can do to help with troubleshooting it, please let me know. :slight_smile: