Cannot enable back-forward cache since v131.0.6778.70 - Githubissues

uazo / cromite

Cromite a Bromite fork with ad blocking and privacy enhancements; take back your browser!

https://www.cromite.org/

GNU General Public License v3.0

3.57k stars 86 forks source link

Cannot enable back-forward cache since v131.0.6778.70 #1649

Closed memchr closed 3 days ago

memchr commented 4 days ago

Preliminary checklist

[X] I have read the README.
[X] I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue.
[X] I have updated Cromite to the latest version. The bug is reproducible on this latest version.
[X] This is a bug report about the Cromite browser; not the website nor F-Droid nor anything else.

Can the bug be reproduced with corresponding Chromium version?

No

Are you sure?

Yes

Cromite version

v131.0.6778.70

Device architecture

arm64-v8a

Platform version

Android 14

Android Device model

OnePlus 10

Is the device rooted?

No

Changed flags

no flags changed

Is this bug happening ONLY in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

No

Describe the bug

Cannot find the back-forward cache toggle in chrome://flags since v131.0.6778.70. This setting can be found in v130.0.6723.117.

Possible related to introduction of policies in Cromite v131.0.6778.70

Steps to reproduce the bug

update 131.0.6778.70

Expected behavior

Not applicable

Screenshots

No response

uazo commented 3 days ago

the back-forward cache is deliberately deactivated by default and should remain so. The problem with the cache is that, in cross-site navigation, it keeps the value of all javascript variables in memory. Since I intend to activate the storage wipe when closing pages, the flag must remain disabled.