Target.createBrowserContext has local-storage bleed through

[mrsk...@gmail.com]

Initially filed here: https://github.com/ChromeDevTools/devtools-protocol/issues/43, but in short I've noticed that local-storage can "leak" between different browser-contexts. It's a bit to setup, but the repro steps are:

1. Connect to Chrome devtools target
2. Create a clean browser context then a new target based upon that
3. Visit a page and set an item in localstorage
   
4. Repeat #2
5. Load the item set in step 3

I'm fairly certain this is a bug as I've not seen the same issue with cookies (haven't attempted with IndexDB or other browser-side storages). Am I mistaken on the intent of this API or is this an issue?

Thanks!

[Eric Seckler]

Definitely not intended. We're aware of the issue and will investigate :)

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=754576

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/f9a2be5c-2157-43c2-b524-2f8f4c95df29%40chromium.org.

[mrsk...@gmail.com]

Thanks! Will follow that thread