Firefox bug - Unrecognized storage name 'null' in about:cache URL

Opening about:cache does not show any entries. The reason seems to be that Private is unchecked. Doing that and trying to update the cache is resulting in an error:

Unrecognized storage name 'null' in about:cache URL

This is actually a Mozilla bug as this happens in a vanilla Firefox as well. But now clicking on Back to overview does give us the cache entries as Private is checked.

added TorBrowserTeam201706R component::applications/tor browser owner::tbb-team priority::medium resolution::fixed severity::normal status::closed tbb-usability type::defect labels

ff45-esr-will-have?

Trac:
Reviewer: N/A to N/A
Sponsor: N/A to N/A
Severity: N/A to Normal

Replying to gk:

Opening about:cache does not show any entries. It's good. But not all entries are Private, even Anonymous ;) The reason seems to be that Private is unchecked. Doing that and trying to update the cache is resulting in an error: {{{ Unrecognized storage name 'null' in about:cache URL }}} That's because URL is about:cache?storage=null&context=p,. Update works if it's not disabled by NoScript. This is actually a Mozilla bug as this happens in a vanilla Firefox as well. But now clicking on Back to overview does give us the cache entries as Private is checked. Hmm, still an issue for ESR45, but not so easy reproducible. STR was found for blocked by NoScript page: check Private, allow page and get about:cache?storage=null&context=. So, it seems only users with weird NoScript config, like in TBB, are affected, because Mozilla knows nothing about it. But the only one ticket with "Unrecognized storage" is great: https://bugzilla.mozilla.org/show_bug.cgi?id=1074485. As this ticket is about usability: about:cache is neither usable, nor reliable, e.g. bugs 469677, 633747, 927919, etc.

Trac:
Summary: about:cache does not show anything in Tor Browser based on ESR 38 to Firefox bug - Unrecognized storage name 'null' in about:cache URL

Replying to gk:

Doing that and trying to update the cache is resulting in an error: Update button doesn't work now for higher sec levels.

Replying to cypherpunks:

Replying to gk:

Doing that and trying to update the cache is resulting in an error: Update button doesn't work now for higher sec levels.

That's #22458 (moved).

bug_16458 (https://gitweb.torproject.org/user/gk/tor-browser.git/commit/?h=bug_16485&id=14d58f8287125b0296e64cd5eebed9c9e6837e96) in my public tor browser repo has a fix for this issue.

Trac:
Status: new to needs_review
Keywords: N/A deleted, TorBrowserTeam201705R added

Moving review tickets to 201706

Trac:
Keywords: TorBrowserTeam201705R deleted, TorBrowserTeam201706R added

r=brade, r=mcs I have trouble making sense of what is displayed in about:cache, but this fix looks okay.

Is there a Firefox bug filed for this issue?

Replying to mcs:

r=brade, r=mcs I have trouble making sense of what is displayed in about:cache, but this fix looks okay.

That's probably due to the interface not being particular intuitive or more on this page being broken. :)

Is there a Firefox bug filed for this issue?

Not yet, I plan to file one later and reference it in this ticket.

Applied to tor-browser-52.1.1esr-7.0-1 and tor-browser-52.1.0esr-7.0-2 (commit e1f39122d16e5cd69dd11732d8fb2faf5087fdd2 and 9607f989206d048c9905d1b19cedf9913750c6c7).

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

Replying to gk:

Replying to mcs:

r=brade, r=mcs I have trouble making sense of what is displayed in about:cache, but this fix looks okay.

That's probably due to the interface not being particular intuitive or more on this page being broken. :)

Is there a Firefox bug filed for this issue?

Not yet, I plan to file one later and reference it in this ticket.

Now it is: https://bugzilla.mozilla.org/show_bug.cgi?id=1371263

closed

moved to tpo/applications/tor-browser#16485 (closed)