Could you provide a site that repro's this issue?

its our cms in prestashop with admin rights. the frontend is ok.
question is what is the difference between previous ver and actual
regarding sending some field and updating db in prestashop database

Prestashop is not a web API, and it's unclear what APIs it's using.  Given that there are thousands of changes between Chrome revisions, any investigation would need a starting place.

Could be a network issue, a forms issue, and anti-malware heuristic, a v8 issue, a navigation issue, etc.

ok, just curious 2week 8h/day 2-3 pc updating our web and yesterday
afternoon stop working all (all same os and chrome) :( today i try find
why, after uninstall the chrome and install the previous ver everything
ok...so i use the previous chrome

Can you contact the developer of Prestashop, and ask to make a small reproduction of the problem?  We can't investigate this issue without reproducing the problem.

I have problem too,
I use Prestashop version 1.6.1.3 and Chrome v54 (Firefox, IE, Chrome V53 work as well)

But I found problem on add/edit product, add/edit member address

I think problem, might have affect with all input box

Thank You

My Firefox 49.0.2 with prestashop 1616 has big delay if saving something
10sec + :( but work. New Opera (41.0.2353.46) cant work , perheps same
problem as chrome 54. IE working fine but higher delay than working 53
chrome.

The same problem in Poland.
Using Prestashop 1.6.1.8, after update to version 54.0.2840.71 m cant add new products normally. 1/10 tries makes adding product successful, rest just refreshing the page.

Same at Edge and mobile chrome.
Working at Firefox and IE
Tested on different computers, 3 various ISPs, at computers where first time anyone visited this site so its 100% Chrome version related.
54.0.2824.0 dev (64bit) problem does not occurs.

How to reproduce problem:
https://youtu.be/l1R9-930qDM 

I am not familiar with PrestaShop at all, but it seems to be
a open, free software, available at:
https://github.com/PrestaShop/PrestaShop

It looks they don't have an issue tracker open to anyone on the
github project page unfortunately, but they seem to have a user
forum at: https://www.prestashop.com/forums/
Can any one of you report the problem there and get PrestaShop's
developers' reply first, as comment #6 suggests?

Here we can only handle Chromium specific, and reproducible bugs
that setting up PrestaShop ourselves.  Ideally a small HTML/JavaScript
snippet that reproduces the exact problem specific to Chromium
is most helpful.

I found this on prestashop site:

https://www.prestashop.com/forums/topic/564155-problems-saving-products/


The solution is to downgrade to Chrome 53 until PrestaShop fixes it in
v1.6.1.9. The problem is because Chrome 54 removed deprecated code that
PrestaShop was still using.

https://www.prestashop.com/forums/topic/564155-problems-saving-products/?p=2431642

im not testet because use chrome 53 xxx but this look useful

Go to:
/admin-url-adressen/themes/default/template/controllers/products/helpers/form/form.tpl

and delete the following:

submitHandler: function (form) {
form.submit ();
},

If somone test this please let now also here.

Thanks for the followup!  Going to go ahead and mark this as a third party issue.

We still not sure if we should take any action or not.

https://www.prestashop.com/forums/topic/564155-problems-saving-products/#entry2431631

This mentioned a deprecated feature was removed. What's that?

I cant test it with new prestashop now. Can anyone test chrome 54 with
new/last presta ?

This solution is working
https://www.prestashop.com/forums/topic/564155-problems-saving-products/#entry2431631

 Issue 663047  has been merged into this issue.

From the prestashop issue it appears to occur in FireFox and Edge as well. If so we wouldn't really consider this a Chrome issue.

I don't see an analysis why this is actually a chrome issue what was the error was occurring and why removing that piece of code (or adding the module) helps the problem.

ie; we want to understand what we changed in the platform that would cause this but it sounds like it fails in other vendors as well so it doesn't sound like we changed anything.

Closing due to lack of feedback and it appears to be an external issue occurring in all browsers.