partition attribute in jsx is absent on rendered view

[lloeki]

this prevents partition from working, leaking cache info and cookies between app and (future) multiple servers.

[geekytime]

So right now the webviews are all running in the same default session, like multiple tabs in Chrome would, I think?

leaking cache info and cookies between app and (future) multiple servers

I think if the webviews are connecting to different protocols/hosts/ports, standard Chromium security would still apply between the webviews, wouldn't it? Only webviews from the same host would share cache and cookies, I think, and the webviews themselves have no knowledge of other webviews running in the same session, do they?

Are you saying you want webviews from the same host to run in different sessions? Or am I just misunderstanding how partitions even work? I'm honestly not 100% certain how they work.

[lloeki]

So right now the webviews are all running in the same default session, like multiple tabs in Chrome would, I think?

It seems so. I've been hitting the issue when having to clear the cache. To do that you have to call webContents.session.clearCache. With partitions, cache (along with cookies and local storage) can be segregated in process and on disk (see inside userData when using a partition, you'll get nested Partitions/foo_partition resembling the default layout in userData).

I'm honestly not 100% certain how they work.

I'm not either, but having one partition per domain for the webframes sounds like a good idea. It also at the very least makes cache clearing easier and per domain, as well as leaving the app-level cache alone in the default session.