Closed jlacher closed 10 months ago
@jlacher
Thank you for reporting this issue.
We already know there are some discrepancies with the way this extension handles partitioned cookies.
Our team is currently exploring some low-level APIs to prevent this kind of mismatch in the data displayed by this extension and the Chrome DevTools. We're also examining a similar issue here: https://github.com/GoogleChromeLabs/ps-analysis-tool/issues/85
We will keep you informed of any progress made on this issue.
@jlacher
This was happening because there were two requests trying to set cookies with the same name but different domains. When we looked closely, we found that the later request was overriding the previous cookie (see screencast)
Therefore, we should avoid the override and list both the cookies. It was implemented and fixed in https://github.com/GoogleChromeLabs/ps-analysis-tool/pull/140 and should be available in the next release. I noticed that the default developer tool also shows both cookies occasionally.
Thank you for the quick response. I would appreciate being kept updated on this issue.
Thank you for the quick response. I would appreciate being kept updated on this issue.
@jlacher The fix is now available as part of version 0.3.0, which we have just released.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Expected behavior The domain as it appears in the Application tab in the Chrome DevTools should be consistent with ps-analysis-tool and the network requests tab
Screenshots
On the ps-analysis-tool:
It can be observed that the domain for _abck is farfetch.net
On the network requests tab:
It can be observed that the domain for _abck is farfetch.net
On Chrome DevTools' Application tab:
It can be observed that the domain for _abck is farfetch.com
Desktop (please complete the following information):
Additional context Add any other context about the problem here.