Characterisitcs not changing image, content or price in browsers

Hi,

On my pc, it works fine on FireFox and Chrome, but it doesn't work on Edge.
So I compared the HTML seen with the inspector tool of each browsers.
Here it is on Chrome: i.imgur.com/AJZFBnB.png
And the same on Edge: i.imgur.com/bf0KqEL.png
So if you compare the two, you can see that inside the main div of the product page (with the itemscope attribute), you have a "form" element on Chrome, which contains the div with the class "row" (and inside all the HTML visible on the product details area of the page), and then some hidden inputs and that's it. And after the form element, you have divs for the variants (with the display:none; inline style on them).
However, on edge, that form element is missing and the HTML of the elements is directly below the main div of the product page and the divs for the variants are also together at the same level.
What this means is that browsers have a hard time parsing the HTML of the area because there is some invalid HTML tags.
And by default, the HTML of HikaShop's product page is valid. Normally, this indicates a problem with either the HTML of the product description or with the customization made to the product page.
Besides that I don't know what it could be. I would recommend to double check your overrides and make sure you clear your website and your browser's cache when you do.

Sure. Please use our contact form for that:
www.hikashop.com/support/contact-us.html

Hi,

So I checked the situation but I didn't learn much.
If I temporarily switch to Cassiopeia, the characteristic system works fine on Edge. So to me, this confirms that the issue is linked to the customization of the product page in the template.
Try on your end, to make sure that you don't have the issue with Cassiopeia on your different browsers.

Then, what you can try is to rename the whole templates/YOUR_TEMPLATE/html folder via FTP to something else in order to disable all the view overrides of your template and check if you still have the issue or not. If you still have the issue, then it's not a problem in an override but something else in the template. I that case, I'm afraid you would have to ask your template provider for help.
Now your could try to cheat, in that case, adding extra </div> tags at the end of the view files of the product page, to try to help the browser to find the correct hierarchy. But you can't add too much of them either or you risk breaking the whole template layout. So you need to proceed one tag at a time and see how it goes.