Replies: 0
Hi there,
I’m Christian, a developer from toolset.com.
We’ve found an issue with Chrome and part of the trigger is WooCommerce. The problem:
– Using chrome.
– Using block editor.
– Having a drafted post with a meta box applied. (can be any, for example https://github.com/christophherr/custom-meta-box-boilerplate)
– Open Developer tools -> Network. Filter for “message”.
– Click on the “Preview” button (left mouse click)
You will see following call in the dev tools:
https://imgur.com/a/2Bk8A1z
The request will never resolve and the servers will work on that request until the tab is being closed.
Anyway the user does not notice any harm yet. But when he further edits the post and clicks on Preview again and again, he will end up with:
https://imgur.com/a/PrKefY3
When clicking once more on Preview, the Preview won’t load anymore. Chrome will just display (in the bottom left) “Waiting for available sockets”.
It doesn’t have to be on one tab. It can also be split over multiple tabs. The 6th click on “Preview” won’t work (as long as the tabs with the pending call are open).
—-
Why reporting here?
WooCommerce is adding no-store
to the Cache-Control header and that’s triggering the issue:
https://imgur.com/a/44sMaXU
Removing the no-store
and it’s working fine again.
I know, it’s probably a Chrome bug and I will also report it there, but to be honest I don’t expect that they will handle it with a very high priority.
And having multiple tabs open while editing a site is not very uncommon, so this bug can become very annoying. (Plus the unnecessary load on the server.)
We (Toolset) will add a function which will remove the no-store
property for that specific page call (action=edit&message=4) – just wanted to let you know, as your clients may also ran into this issue and maybe you do not require the no-store
parameter at all (which I guess from the comment in the source code).
Have a nice day,
Christian