Today I was starting to tweak some parts of a couple of my sites when I ran into this strange bug. When I expanded the Spacing settings for a couple of containers I was not able to edit all of the properties. As the GIF below shows some of the values can be clicked on to expose the dropdown, but others are not responsive.
I tried this in a couple of different projects and got the same behavior. I did restart the app a few times and on one occasion got it to work briefly, but then it stopped again.
Very strange.
As you can see it tends to only be the BOTTOM margin, TOP padding, and BOTTOM padding dropdowns that do not work. The others all work as expected.
I have never seen this until today and I can’t imagine why this would start happening all of a sudden. Next, I will try getting a fresh copy of the app with the hopes that will resolve the issue.
Downloaded a fresh copy of Elements, now without the Rapidweaver name in it, and the problem persists. I also discovered that in most cases it does not work on either of the right dropdowns.
Could you provide a sample project and the steps you take to reproduce this? once we have this we can see if we can re-create the issue and get it fixed here!
@dan Well of course today it is working just fine. If it shows up again I’ll immediately bag up the project and send it to you. But for now it seems to have resolved itself. Very strange.
@dan This issue resurfaced again today. I had dragged out your FAQ template and was editing the first accordion when the padding control froze for the TOP and BOTTOM. Left and right work no problem.
I quit the app and restarted and the problem still persisted. I’ll email you the project, so you can take a look. Hopefully, it will persist across the cloud.
@dan Moving, duplicating, or copying and pasting does not resolve the problem.
The solution I could find was to move the Settings panel to a different location within my workspace layout, and then it would work. But on returning it to the original location it would stop working again.
I have never had much luck reproducing it, but it is consistent for me in that file. I’ll keep quitting and restarting to see if it eventually goes away, as it has done in the past.
Glad it’s working now, but it’s defiantly something we’re going to keep an eye!
If you ever manage to work out some re-producible steps or have a hunch what’s causing it, let us know as it all helps us in tracking down and squashing these pesky issues.
