I noticed a weird behaviour when I styled my elements with global classes.
When a global class is active for styling, it doesn’t take effect immediately as soon as I change the value. It works fine when we style the element not using the global classes.
Refer to the screencast
Easier to understand.
- WordPress version: 6.0.3
- Gutenberg Plugin version: -
- Cwicly Plugin version: 1.2.3
- Cwicly Theme version: 1.0.3
A page refresh fixes the issue itself.
Even though a refresh would fix this issue but when it would return when I stay on the page for some time(hours).
But I think this is not supposed to be. Or is the issue caused by Gutenberg?
Sorry for not getting back on this one.
Are you still experiencing this issue?
If possible, could you let me know how to consistently reproduce it as I cannot seem to reproduce it on my end.
Thanks in advance.
Thank you for checking back on this missing thread.
Yes. I still see this when I am on the page for quite some time. I tested it again this morning and saw the same. It’s difficult to tell you how to reproduce to see this.
Thanks for letting me know.
This is a difficult one for me to reproduce.
We are onto it, as @Araminta has experienced it, but can’t yet find what is bugging.
Hmm, something like this happened to me the other day too.
Layout changes on an element weren’t being reflected either in the back-end or front-end, but once I added a margin to the element it all snapped back to life again.
I’ll see if I notice a way to reproduce as well.
Thanks @sunny, much appreciated!
Just to make sure, this was happening on a global class?
Yeah, it was a global class.
It’s glad to know that @Araminta experienced the same. So you guys know. Looking forward to the fixes soon.
Still working on this one.
It is a top priority to get it fixed as soon as possible so please bear with us.
Thanks for your patience!
We’ve released what we hope if a fix for this hard to come by issue in 188.8.131.52.
I’d be grateful, whenever you have time, if you could let me know if it helps on your side or if you still encounter the issue.
Thanks @Louis, for the fixes!
I will keep trying to see if it persists.
Bringing this issue back up to light and was wondering if you experienced it again since update 184.108.40.206?
I’ll be moving this to fixed, but if you do still encounter this issue, I’d be grateful if you could let me know by replying to this thread.
Thanks once again for taking the time to report these issues.
Thank you for the follow-up on this issue!
Recently, I don’t seem to see this issue anymore since the mentioned version!
Thanks @jornes, really appreciate your reply!