alessiog

You are right, that this is one of the reasons for reviews and of course you have all the rights to write a review first. Although I think you are not doing yourself a favor as our communication starts with a slap in the face for us. Even if you apologize afterwards (= changing the review to a higher rating) this will be a bad start.

That’s true. Although I didn’t write the review to get support – when I noticed the issue, I just replaced the plugin. But you’re right, I certainly don’t want to have a bad start and make you feel bad especially when you’re trying to get to the bottom of the issue, so I’ve changed it into a 5-star review for now.

I’ll make some more tests and create a GitHub issue with further information!

Hi Torsten,

Thank you for your reply! Please don’t take my review in a disrespectful or attacking way. I appreciate you developing this plugin.

The main reason for writing this review is to warn other people that it might cause CLS. I didn’t think much further about it. And honestly, I don’t see anything wrong with that. I did spend a few hours figuring out which plugin specifically caused these issues – I might as well share it with others – it might help someone. That’s what reviews are for?

I always read other reviews before downloading a plugin to see if other people encountered any issues and I do appreciate that people write them.

In my opinion, it starts to be immoral if the reviewer doesn’t change the review after the author tries to address it. I know that many reviewers do that, so those 1 star reviews definitely have a bad stigma for developers, but I won’t be that person.
Once the issue is addressed, I’ll happily turn it into a 5 star review.

Yeah, creating a support ticket or a GitHub issue first is the nicer option, and I usually try to do that.
But I don’t think it’s right to blame someone for writing a bad review immediately as well, unless the reviewer is completely unresponsive and doesn’t want to change it. This is what reviews are for.

What do you think? I’m open to change my mind.

Also, I’ll make sure to send you more detailed information about the issue tomorrow. Is this thread here fine, or do you prefer if I open a GitHub issue or a support topic?

I’m using GeneratePress as a theme. Their support told me it’s likely a plugin causing it. I did multiple tests with Antispam Bee, and every time it was enabled, the CLS shift happened. Once I disabled it, the issue disappeared.

Kind regards,

Alessio