Hi there @tjendol,
I tested this on my local environment but couldn’t reproduce this with WooCommerce 3.6.5 and the Storefront theme:
(screenshot)
https://cld.wthms.co/fY3cuq
I tested both with a default variation value as well as adding the attribute in the URL as a query string but both times I had the ‘Clear’ button visible.
I would suggest running a conflict test using a default theme and with just WooCommerce activated.
Hi @tjendol
I hope the suggestions we passed along to you in the previous reply guided you in the right direction. I’m fairly certain that a conflict test should help you in uncovering the problem.
In case you’re unsure of how to do a conflict test, feel free to try out the steps in the following document: https://docs.woocommerce.com/document/how-to-test-for-conflicts/
Since we haven’t heard from you in a while, we’re marking this thread as Resolved for now.
Please feel free to reply to us in this thread, should the problem persist. We are happy to look into this and guide you further.
All the best!
Thanks for your replies!
I wonder if it has something to do with the way I set up my product selection.
I have two dropdown fields, one for product type and one for size. Different product types can have different sizes.
When I have a default variant set, the clear option does not show. When no default value is set, the clear option shows as expected.
I found out the clear option reappears when I set both fields to “choose an option” and next change them to a different option. Then the “clear” option shows again.
Obviously, this is a terrible user experience.
Anyway, disabling the default product selection now seems the only solution for me.
Thanks again!
Hi @tjendol!
Thanks for getting back to us and for the feedback.
I tried testing this out in my local site – I first set a default option for the color attribute as red: https://cld.wthms.co/a0ftzu
Next, I tried loading that page. As you can see in the screenshot below, the clear option not only appears but that it seems to work as well, as you can se in the following screencast: https://cld.wthms.co/zx4quR
On the same variable product, I tried testing with two variations and got the same result: https://cld.wthms.co/nPtpfZ
Based on these results, I would still think that the problem has something to do with nuances in your site, as we were not able to replicate it locally. Feel free to try testing with a new product, to see if you find the same problem. Also, look for any console errors when you test this, to see if it reappears.
.
