Status Update
Comments
an...@google.com <an...@google.com> #2
Hi test team, this appears to be a regression, making it a good candidate for bisection to quickly identify the root cause. Please remove 'Needs-Bisect' hotlist and provide a rationale if bisection isn't applicable; this feedback will improve the automated system.
an...@google.com <an...@google.com> #3
Suggested Component Path:
Public Trackers > 1362134 > Chromium > Platform > DevTools > Application
If the suggested component is incorrect or you have any feedback, please use
is...@gmail.com <is...@gmail.com> #5
I'm using Chromium through WebView2 and Electron. I mentioned that version above. Started happening in 133.0.6920.0, continues in 134. I'm on Windows 11. I will link to some minimal example later when I get a chance.
pe...@google.com <pe...@google.com> #6
Thank you for providing more feedback. Adding the requester to the CC list.
is...@gmail.com <is...@gmail.com> #7
easiest way, on my end at least, to repro this is to follow the repro steps listed here:
https://github.com/MicrosoftEdge/WebView2Feedback/issues/5185
or
https://github.com/electron/electron/issues/46428
(here, you'll want to download Electron Fiddle and load the gist link in that's listed in the issue report)
or
(here, you'll want to download Electron Fiddle and load the gist link in that's listed in the issue report)
ka...@google.com <ka...@google.com> #8
Tested the issue on Linux debain using chrome version 135.0.7049.52 with the below steps
1. Openexample.com
2. execute this code code to add a normal and a partioned cookie to theexample.com frame: cookieStore.set({ name: "Normal-Cookie", value: "normal-value", secure: true, path: "/", sameSite: "none" });cookieStore.set({ name: "Partitioned-Cookie", value: "partitioned-value", secure: true, path: "/", sameSite: "none", partitioned: true })
3.Check the cookies in application tab
4. go back to previous page or refresh
5.observed that the cookies are cleared withou any issues
please find the attached screencast and confirm if anything missed here.
Request you once try the issue by upgrading chrome to latest stable and update the thread if the issue still persists.
Thanks,
1. Open
2. execute this code code to add a normal and a partioned cookie to the
3.Check the cookies in application tab
4. go back to previous page or refresh
5.observed that the cookies are cleared withou any issues
please find the attached screencast and confirm if anything missed here.
Request you once try the issue by upgrading chrome to latest stable and update the thread if the issue still persists.
Thanks,
is...@gmail.com <is...@gmail.com> #9
My issue is not with going back to another page, it's specifically with using the Storage.clearDataForOrigin CDP function to clear the cookies in example.com . Can you try using that API?
pe...@google.com <pe...@google.com> #10
Thank you for providing more feedback. Adding the requester to the CC list.
ka...@google.com <ka...@google.com> #11
Seems the issue requires to test with API which is out of TE scope hence adding TE-NeedsTriageHelp
Requesting dev team please look into this issue.
Thanks,
Requesting dev team please look into this issue.
Thanks,
Description
Steps to reproduce the problem
Problem Description
I use Storage.clearDataForOrigin to clear partitioned cookies to work around this WebView2 issuehttps://github.com/MicrosoftEdge/WebView2Feedback/issues/4669
This worked in version 132.0.6834.210, but stopped working in 133.0.6920.0 Wonder if this chromium commit broke this:https://chromium.googlesource.com/chromium/src/+/ef0eba18e45cbafff9f351b280d780fdb0f2a012
Summary
Storage.clearDataForOrigin no longer clears partitioned cookies
Additional Data
Category: Developer Tools
Chrome Channel: Stable
Regression: Yes