Can cookie storage in `Local Storage` & `File system` be BLOCKED?



  • @Pathduck Ta. Only a partial response; tis v late here & i am beginning to see double...

    This is what the documentation says:

    Expression Options
    Uncheck 'Keep LocalStorage' on New Greylist Expressions
    Default: Disabled

    For those who want to always default to clean LocalStorage on browser restart for that site.
    Only affects NEW expressions. Existing ones will keep their current settings.
    Uncheck 'Keep LocalStorage' on New Whitelist Expressions
    Default: Disabled

    For those who want to always default to clean LocalStorage whenever the automatic cleaning happens for that site.
    Only affects NEW expressions. Existing ones will keep their current settings.

    Maybe i have misunderstood it? I took these to refer only to the local storage behaviour for my grey- & white-listed sites... & as such, those few are the ones that i do want to retain their cookies. Per my OP, it is all the other sites whose cookies i want to not be stored, or at least auto-removed during the session or at start of next session.

    @Pathduck said in Can cookie storage in `Local Storage` & `File system` be BLOCKED?:

    Clear cookies and site data when you quit Vivaldi = Enabled

    I had (wrongly) assumed this was your setting all along

    That indeed HAS been my longterm setting. It's just that stupidly chromium seems to toggle it each time i change the master switch from allow cookies to block all cookies.



  • Well, it had been going great all day, exactly as i'd hoped... but now it's failed again:

    ![0_1593500628226_2020-06-30, 17-02-26.png](Uploading 100%)

    ![0_1593500440333_d030b6c0-f8dc-40af-a990-0dc2680cceae-image.png](Uploading 100%)

    ![0_1593500571995_2020-06-30, 17-02-26.png](Uploading 100%)

    Gaaaah!

    PS: This forum software fails so frequently for uploading images!



  • @Steffie I suspect if you look at the content of these entries they will say "None / 0 B".

    I suspect a Chromium bug 🙄



  • @Pathduck Good idea, i'd not thought to look at it that way. Fwiw:

    edition.cnn.com locally stored data
    Remove All
    File system
    Origin
    https://edition.cnn.com
    Persistent storage
    None
    Temporary storage
    0 B
    Database Storage
    Origin
    https://edition.cnn.com
    Size on disk
    4.7 KB
    Last modified
    Thursday, 2 July 2020 at 13:50:02
    
    mashable.com locally stored data
    Local storage
    Origin
    https://mashable.com
    Size on disk
    27 B
    Last modified
    Thursday, 2 July 2020 at 13:18:40
    
    www.reddit.com locally stored data
    Remove All
    File system
    Origin
    https://www.reddit.com
    Persistent storage
    None
    Temporary storage
    0 B
    
    www.thefarside.com locally stored data
    Remove All
    Local storage
    Origin
    https://www.thefarside.com
    Size on disk
    12 B
    Last modified
    Thursday, 2 July 2020 at 11:19:02
    
    www.theguardian.com locally stored data
    Remove All
    File system
    Origin
    https://www.theguardian.com
    Persistent storage
    None
    Temporary storage
    0 B
    

    🤷♀



  • @Steffie I have no idea, I also get some unexplained entries in the siteData page that should've been removed. These show only File System and zero actual data:

    Persistent storage
    None
    Temporary storage
    0 B
    

    Your entry for Reddit, Guardian is similar, your other examples have DB or Local storage, no idea why those haven't been removed.

    Some light reading on the issue:
    https://www.html5rocks.com/en/tutorials/file/filesystem/#toc-requesting-quota
    https://developer.mozilla.org/en-US/docs/Web/API/Window/requestFileSystem
    https://security.stackexchange.com/questions/177591/are-chrome-file-system-api-not-supercookies-why-are-people-not-worried-about-th

    "To use PERSISTENT storage, you must obtain permission from the user to store peristent data. The same restriction doesn't apply to TEMPORARY storage because the browser may choose to evict temporarily stored data at its discretion."



  • I assume vivaldi works differently to vanilla chromium.
    What i did with chromium is block all cookies and storage and allow per site if it caused an issue.

    Firefox works better than chromium in this regard.
    I don't like the way chromium adds search engines by it self too.
    You could of course install an extension..cache history cleaner is a good example.

    Also there are flags which can be disabled like file handling etc,not sure if they work though.

    I find this behavour disturbing too but i don't think it id for nefarious uses.If you visit a number of sites regularly and they need to set local storage then persistent clearing would seem pointless.


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.