Mike, have you already started working on it? Because it would likely conflict with https://bugs.chromium.org/p/chromium/issues/detail?id=700791 which I'm going to start working on. (Because CWVWebViewConfiguration should own browser state instead.)
I had started, but stopped once I ran into issues with creating the browser states at allocation time of the DataStore. I don't have any saved progress on this task, so I set the status back to Assigned. Feel free to continue with the merge of the objects in 700791. Thank you for checking!
Update to this bug:
As discussed above, CWVWebViewConfiguration should own the BrowserState instead.
Also, after this change, +defaultConfiguration and +incognitoConfiguration should return a new instance of CWVWebViewConfiguration (with a new instance of BrowserState) each time, instead of returning a singleton.
Comment 1 by ichikawa@chromium.org
, Mar 13 2017