1467463 - Storage Inspector cannot delete cookie in private browsing mode

Status: NEW

(DevTools :: Storage Inspector, defect, P2)

Description

[Martijn]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180604143143

Steps to reproduce:

A cookie gets created, and I want to delete it. I go to the Dev Tools, tab Storage open Cookies in the left pane, select the correct domain, and find the cookie I want to delete. I right-click it, and select "Delete <name>".


Actual results:

Nothing. Cookie isn't deleted. Neither after a reload (cookie does NOT get created on page load) nor after a restart. This is the case for HTTP and HTTPS protocols. It also goe for cookies create through javascript on a static html file loaded via file://. In short: this problem goes for every cookie on every page everywhere always.


Expected results:

Cookie should be deleted when I select the delete option on it.

Comment 1

[Martijn]

A workaround is to edit the name & value of a cookie and empty them.

Comment 2

[ariasuni]

This bug is happening to me for a long time, and I only noticed recently that it’s only in private browsing mode.

Comment 3

[ariasuni]

It does happen too in not private browsing mode. In my case, the cookies are indeed deleted but they still appear in the devtools and I need to close and reopen the devtools to see that they are indeed gone.

Comment 4

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

@Martijn I cannot reproduce this... is there a particular test page it happens on for you?

Comment 5

[Alex Angas]

(In reply to Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe] from comment #4)

@Martijn I cannot reproduce this... is there a particular test page it happens on for you?

Clearly I'm not @Martijn but hoped with the no repro comment that this bug was fixed!

Unfortunately I can reproduce on any page that creates cookies when browsing with In Private mode. Tested using both Firefox 64.0.2 and Firefox Dev Edition 66.

Comment 6

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

@Alex Angas Thanks for that... I can reproduce the issue in private browsing mode.

There are no errors when trying to delete a cookie but the following appear as the storage inspector is loading:

console.warn: "Failed to enumerate localStorage for host about:privatebrowsing: [Exception... \"Component is not available\"  nsresult: \"0x80040111 (NS_ERROR_NOT_AVAILABLE)\"  location: \"JS frame :: resource://devtools/server/actors/storage.js :: populateStoresForHost :: line 1173\"  data: no]"
console.warn: "Failed to enumerate sessionStorage for host about:privatebrowsing: [Exception... \"Component is not available\"  nsresult: \"0x80040111 (NS_ERROR_NOT_AVAILABLE)\"  location: \"JS frame :: resource://devtools/server/actors/storage.js :: populateStoresForHost :: line 1173\"  data: no]"
console.warn: "Failed to enumerate CacheStorage for host about:privatebrowsing: SecurityError: The operation is insecure."
console.warn: "Failed to enumerate CacheStorage for host https://www.google.com: SecurityError: The operation is insecure.

So at the very least localStorage and cacheStorage need to be disabled in private browsing mode.

I know cookies are stored in memory in private browsing mode so I am assuming that we have to delete them in a different way.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:Honza, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Comment 11

[BugBot (nomail) [:suhaib / :marco/ :calixte]]

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Comment 12

[simon.rochwerg]

I can confirm that this bug is still present and relevant in firefox 118.
I'm surprised that we had a perfect feature in older firefox versions (edit and resend -> modify cookies on the fly)

I cannot understand why this feature was removed.
In my opinion there is an agenda to limit developers capability to debug websites.

Comment 13

[Martijn]

I haven't checked recently. But the point shouldn't be to somehow find a repro case.

The point is that a cookie should always be deletable in the devtools, no matter what. So if there's any condition under which a cookie is not getting deleted, please remove such condition. Devtools means you're assuming all control over a website, essentially, and there should not be any hindrances of any kind to fiddle to one's heart's content.

So with that, I'm not sure why I'm tagged with a needinfo.