-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Facilitate Navigation from Cookie to Corresponding Network Request #320
Comments
@amovar18 The added functionality looks good to me. but I have some minor UI feedbacks to share which can be addressed later.
Instead of Note Note for me: Test it in both themes after the fix is added |
Thanks @kjnanda for pointing this out let's make an enhancement issue for this the context menu used everywhere else is styled the same.
This should also be part of the enhancement issue mentioned above. |
Released as a part of v0.4.0, closing this issue. |
Feature Request
Description:
This feature aims to enhance the user experience by providing a seamless way to navigate from a cookie listed in the PSAT Extension to its corresponding network request in the network panel. The process would be facilitated by generating a query string from the selected cookie and its domain, which can then be copied to the clipboard for easy pasting in the Network tab.
Motivation:
The primary motivation for this feature is to streamline the workflow for users who need to track how specific cookies are used in the network requests. By simplifying this process, users can more efficiently analyze and debug web applications, leading to faster debugging of cookies in the Network tab of Chrome Dev Tools.
User Story:
As a web engineer, I want to quickly navigate from a selected cookie in the Cookie table of PSAT Extension tab to its corresponding network request, so that I can efficiently analyze how the cookie is being used in the network activity of my web application.
Acceptance Criteria:
Additional Information:
Example query string:
The text was updated successfully, but these errors were encountered: