Project

General

Profile

Actions

Bug #1242

closed

Update directories so Clear DOM Storage detection works correctly again

Added by Soren Stoutner 15 days ago. Updated 14 days ago.

Status:
Closed
Priority:
Next Release
Start date:
12/06/2024
Due date:
% Done:

0%

Estimated time:

Description

It looks like WebView recently moved all the directories to a subdirectory of `Default`.

This caused Clear DOM Storage to always show ghosted, even when there was something to clear.

Clear and Exit still cleared all DOM storage, but it wasn't possible to just clear DOM storage while the app was running.

Actions #1

Updated by Soren Stoutner 15 days ago

  • Description updated (diff)
Actions #2

Updated by Soren Stoutner 15 days ago

  • Tracker changed from Feature to Bug
  • Status changed from New to Closed
Actions #3

Updated by A bughunter 14 days ago

It is worth giving me credit for the bug report https://redmine.stoutner.com/issues/1241#change-4233 . Rather not discredit me because of lacking documentation having no way to explain the bug. Sometimes your, Soren, feelings can be decieving.

Soren Stoutner wrote:

It looks like WebView recently moved all the directories to a subdirectory of `Default`.

This caused Clear DOM Storage to always show ghosted, even when there was something to clear.

Clear and Exit still cleared all DOM storage, but it wasn't possible to just clear DOM storage while the app was running.

Actions #4

Updated by Soren Stoutner 14 days ago

To be fair, your bug report wasn't really that the DOM Storage status wasn't being updated by Privacy Browser. In fact, nothing in what you wrote indicated that at all.

It was only that I tend to double check things that I decided to verify that the DOM Storage status check was still working. Mostly because this isn't the first time Android's System WebView had modified the directory structure to make the check stop working.

Actions #5

Updated by A bughunter 14 days ago

fair, quite contrare, because of lacking documentation having no way to explain the bug I gave possibly the best bug report.

Soren Stoutner wrote in #note-4:

To be fair, your bug report wasn't really that the DOM Storage status wasn't being updated by Privacy Browser. In fact, nothing in what you wrote indicated that at all.

It was only that I tend to double check things that I decided to verify that the DOM Storage status check was still working. Mostly because this isn't the first time Android's System WebView had modified the directory structure to make the check stop working.

That's good for you.

Actions

Also available in: Atom PDF