Bug 31157 - Web Inspector: support editing cookie key/values from inspector
Summary: Web Inspector: support editing cookie key/values from inspector
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Enhancement
Assignee: Nobody
Keywords: InRadar
Depends on: 156091
  Show dependency treegraph
Reported: 2009-11-05 01:44 PST by Jonas Due Vesterheden
Modified: 2019-02-12 11:39 PST (History)
10 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Jonas Due Vesterheden 2009-11-05 01:44:41 PST
It would be great if it was possible to edit and delete cookies in the Storage section of the web inspector.
Comment 1 Timothy Hatcher 2009-11-05 02:05:36 PST
You can delete. Edit will be harder.
Comment 2 Jonas Due Vesterheden 2009-11-05 02:11:06 PST
Sorry, I managed to overlook the 'X'-button!

Would it be possible to bind backspace to "Delete cookie"?
Comment 3 Brian Weinstein 2009-11-05 09:53:30 PST
(In reply to comment #2)
> Sorry, I managed to overlook the 'X'-button!
> Would it be possible to bind backspace to "Delete cookie"?

That would be useful, if you want to file a new bug and assign it to me, I can take a look at it today or tomorrow.
Comment 4 Brian Weinstein 2009-12-09 13:23:18 PST
Delete is now bound to delete cookie as of http://trac.webkit.org/changeset/50613.
Comment 5 timmywil 2011-03-02 13:18:38 PST
It would be awesome to be able to delete more than one cookie at a time on a site.
Comment 6 Radar WebKit Bug Importer 2014-12-17 11:22:55 PST
Comment 7 Brian Burg 2015-11-18 10:39:53 PST
The DataGrid editing should just be a flag, and the backend will need a new "setCookie" command in Page.json. That's the easy part.

If we only support editing name and value, then that can be implemented as a delete + adding a new cookie via Document.cookie= under the hood.

If editing other fields is to be supported, or loading/saving cookies to file, then a new CookieJar method is needed that takes in the various header fields and makes an already-parsed cookie. This could be nontrivial depending on the port.
Comment 8 Bem Jones-Bey 2019-02-12 11:39:21 PST
I recently ran into this issue, and it forced me to use Firefox/Chrome to test some code I was working on.

Editing just the name and value would be sufficient for me, and seems like it might be sufficient for this issue given that it specifically says key/value in the title. If there is agreement that that simple path is good enough, I may try my hand at putting together a patch for this.