From another thread it looks like this is being worked on currently, the elements inside that cause the issue with the nth-child should be being moved out.
Yes, that’s the problem. The ul.actions which show the edit button, padding, width etc. in every element and temporary style tags cause problems in the case of nth-child or partly also nth-of-type, because they are part of the DOM and the “calculation” doesn’t work anymore.
I’m using a first-of-type pseudo class on the repeating element (query loop), and while it does render fine on the front-end, it’s buggy on the backend. If the pseudo class is not selected in the builder, displays correctly, but once I select it (pick from the existing applied pseudo classes), it applies the styling to all other repeating elements as well. I guess it’s more like an undesired side effect, than a real bug.
Thanks for developing Bricks! It’s becoming a geat builder!
Thanks for the welcome message! I’m already so flattered by the whole forum and the conversations I see here. It’s something that reminds me of the good old days of phpBB communities
Looking forward to work with Bricks and do my part on helping it become the best page builder ever!
Ah very interesting! Glad it seems improved, that’s not my experience though unfortunately.
I’m wondering… maybe it’s fixed just for new pseudo classes but not existing ones? Here’s a quick video of what it looks like for me with the existing pseudo class. Everything is good until I open a style menu item then it applies it to every instance even if I didn’t change anything. Not sure why it’d trigger like that just by simply opening a style item without actually making any changes to it, but I think that shows there’s still a bug here.
When I get a bit more time I’ll see if I can narrow down if the issue applies only to existing pseudo classes but maybe fine for new ones only, may help narrowing down a root cause.
It isn’t a template, it’s a page. I’m not certain how to get the JSON, are there steps for that and does it apply still if it’s a page? I’ll get it for you if I can figure it out, haha
Ah thank you, I just tried that now, emailed the JSON to you a moment ago (wasn’t sure if it was secure to post here or not). Thanks for looking into this.
Me too. Hopefully we’ll find out in the next release candidate for 1.5. I know @timmse had told me he couldn’t reproduce it but was using the latest code which was newer than the 1.5 beta, so it’s possible it’s fixed in newer updates to the beta, and hopefully we can confirm in the 1.5 RC coming out later this week.