You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open the following product in the backend "adidas Consortium Campus 80s Running Shoes"
Navigate to the product attributes section
Select the color product attribute
Go to the condition section
Select a condition for the attribute, i.e. for "Size" and value "8"
Save the page
Open the following product in the frontend: "adidas Consortium Campus 80s Running Shoes"
Potentially refresh the page multiple times
Immediately after the page you load, you will see the "color" product attribute a small amount of time, before the JavaScript kicks in.
Imagin having about 6 product attributes assigned to a product, most of them with a condition on another product attribute. After the page loads the customer will initially see a very long list of product attributes for a short moment, even though he might only be required to select a few of them.
For our customer this has already caused multiple of his customers complaining that the page is moving this much but not showing everything. Some customers even thought that this might be a bug.
We would expect that the visibility check for the product attributes is already checked on the c# side, during the rendering of the page. That would cause a much smoother customer experience.
The text was updated successfully, but these errors were encountered:
nopCommerce version: 4.60.x
Steps to reproduce the problem:
Immediately after the page you load, you will see the "color" product attribute a small amount of time, before the JavaScript kicks in.
Imagin having about 6 product attributes assigned to a product, most of them with a condition on another product attribute. After the page loads the customer will initially see a very long list of product attributes for a short moment, even though he might only be required to select a few of them.
For our customer this has already caused multiple of his customers complaining that the page is moving this much but not showing everything. Some customers even thought that this might be a bug.
We would expect that the visibility check for the product attributes is already checked on the c# side, during the rendering of the page. That would cause a much smoother customer experience.
The text was updated successfully, but these errors were encountered: