Describe the bug
On checkout page, for a shop with multiple countries available, you can use the country dropdown to select your country. When you do so, an ajax request is performed to /order?ajax=1&action=addressForm. This returns the updated HTML form which is then inserted into the checkout page.
But when it does so, it does replace everything. So if you perform this dropdown multiple times you see the template grow bigger and bigger 馃槃.
To Reproduce
Steps to reproduce the behavior:
develop branch, enable at least 2 countries from BO. You need to be able to choose a country in the checkout page./commandecheckout-addresses-step it looks like this
checkout-addresses-step. Now it looks like this 馃槃 
Additional information
PrestaShop version: develop
PHP version: php7.2
It's harmless because it's only html comments. But it's not very clean either.
These comments came from the debug mode to help developers to create themes and are not displayed in production. Because a comment could not be selected with selectors I'm not sure we're able to do something :/
These comments came from the debug mode to help developers to create themes and are not displayed in production.
Considering this, then this is 100% harmless
Hi @matks,
I have the same issue with develop branch.
With PS1752, it is OK.
Thanks!
@matks Is it a regression of 1.7.6.0 ?
If yes, we should add it to the 1.7.6 backlog
@matks Is it a regression of 1.7.6.0 ?
If yes, we should add it to the 1.7.6 backlog
I dont know, but anyway this is really harmless. Nothing bad can come of it, it's just a "clean code" issue.
Yes, this is really harmless. In fact, as I understand, we use the replaceWith jquery function (https://github.com/PrestaShop/PrestaShop/blob/develop/themes/classic/_dev/js/listing.js#L153) with the new content:
<!-- begin my-template.tpl -->
<div id="content">blabla</div>
<!-- end my-template.tpl -->
because comments are not selected, it's added again, and again, each time we use this kind of replacement.
@marionf @khouloudbelguith I'm able to reproduce the bug in 1.7.5.2, so this is not a regression and I think can be remove from 1.7.6 backlog

I close as I think it's insignificant
Most helpful comment
@marionf @khouloudbelguith I'm able to reproduce the bug in 1.7.5.2, so this is not a regression and I think can be remove from 1.7.6 backlog
