Story sharing and unsharing does not work on Chrome

[cproctor]

On Chrome, but not on Firefox, clicking "share" or "unshare" on a story appears to work (the reloaded page claims the change took effect), but the change does not actually take place--loading the story in another browser or reloading the page shows that the change did not take effect.

[cproctor]

Confirming that the issue can be reproduced in the local development server.

[cproctor]

One difference in behavior I am seeing: When I insert a breakpoint intoShareStoryView.post, Firefox hangs until I allow the request to continue. Then Firefox follows the 302 redirect back to the story page and issues a get request as expected.

"GET /stories/15060/ HTTP/1.1" 200 18701

Chrome, in contrast, immediately fires off a post request (the network tab of Chrome's debugger shows the compile request being sent first).

"POST /stories/15060/compile/ HTTP/1.1" 200 439

Headers

I don't see any likely issues here. Chrome has a no-caching header (because I had the debug toolbar open); this should not be an issue as this is a POST request.

Firefox headers for POST Share:

{
  'Content-Length': '84', 
  'Content-Type': 'application/x-www-form-urlencoded', 
  'Host': 'local.unfoldstudio.net:8000', 
  'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0', 
  'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8', 
  Accept-Language': 'en-US,en;q=0.9', 
  'Accept-Encoding': 'gzip, deflate', 
  'Referer': 'http://local.unfoldstudio.net:8000/stories/15060/', 
  'Origin': 'http://local.unfoldstudio.net:8000', 
  'Connection': 'keep-alive', 
  'Cookie': 'csrftoken=STOyWBTQG7dJMv9hAgqbjBQRnrA6wVLh; _pk_id.2.a9eb=601b99cc48c899ef.1746653839.; sessionid=z71ozdjltr9w5gx2as3ep9ujpd92xki4', 
  'Upgrade-Insecure-Requests': '1', 
  'Priority': 'u=0, i'}

Chrome headers for the same request:

{
  'Content-Length': '84', 
  'Content-Type': 'application/x-www-form-urlencoded', 
  'Host': 'local.unfoldstudio.net:8000', 
  'Connection': 'keep-alive', 
  'Cache-Control': 'max-age=0', 
  'Origin': 'http://local.unfoldstudio.net:8000', 
  'Upgrade-Insecure-Requests': '1', 
  'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36', 
  'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7', 
  'Referer': 'http://local.unfoldstudio.net:8000/stories/15060/', 
  'Accept-Encoding': 'gzip, deflate', 
  'Accept-Language': 'en-US,en;q=0.9', 
  'Cookie': 'csrftoken=HbH9W5kL7zIpTygYKUlvEKvNCPdIVHLS; sessionid=e55eixhbio3e2voj3wv49s23uav7hpx9'
}

[vbhtt]

I noticed similar behaviour in both Chrome and Firefox when it comes to the order of the requests. Both send the compile request first which fail due to an error

Firefox fails with NS_BINDING_ABORTED:

Chrome fails with an 'unknown' status code and a helpful tooltip:

There is no issue with nested form elements, as the compile request is made from app.js through jquery.

The next thing to do would be to figure out what this NS_BINDING_ABORTED/unknown status code error is, and why the async presave_story function doesn't seem to be working properly

[vbhtt]

It needs to be tested properly, but removing this line seems to fix the bug.

The actual fix for this issue should be to figure out how to make the presave function work async instead of just removing it.