UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Open dev tools
2. Switch to network tab
3. Load any page that loads components off of other domains which would either normally have the "Cookie: " header in the request or have the "Set-Cookie:" header in the response

What is the expected behavior?
When clicking on the request and looking at the "Headers" section I'd expect to see the "cookie" and "set-cookie" headers as normal. I'd also expect that right-clicking on the request and selecting "Copy as cURL" would produce a command with "-H 'cookie: ...'" arguments to curl.

What went wrong?
The request headers don't include any "cookie:" headers, and the response headers don't include any "set-cookie:" headers. The request headers also has the warning: "Provisional headers are shown".

Copying as cURL omits any cookie headers.

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

The cookies are being set properly as show in the Application -> Cookies section of dev tools. And as shown by the requests and responses shown in chrome://net-internals/

This site details the issue nicely with a work-around (disable site isolation): https://blog.ermer.de/2018/06/11/chrome-67-provisional-headers-are-shown/