31
[fixed, caused by filter list within uBlock Origin] What happened to the back history caching in 120 or 121? (lemmy.dbzer0.com)
submitted 2 years ago* (last edited 2 years ago) by Redjard@lemmy.dbzer0.com to c/firefox@lemmy.ml
9 comments fedilink hide all child comments

I updated my firefox from 119.0.1 to 121.0 two days ago, and have noticed a for my usage quite significant change:
When I have a page, say a search engine query or a gallery of links on a page, and I open one then go back, previously I got the cached version. Within reason of the cache size I could go back a few pages even days later and critically see them as they where, just like I would expect for a tab I have open.

I use this behavior to work through essentially todo lists, so now that the lists get reloaded every time I visit them, this combines with server side caching to make the list jump around quite annoyingly.
My expected behavior would be the cached back history being served when available, except when I manually hit F5.

Was this change intentional? Is there any way to get the old behavior back?

Edit:
It seems to be a bug and only happen on some profiles, potentially dependent on some metric related to heavy use, like number of open tabs and windows.
Edit:
It seems to be related to uBlock Origin.
Edit:
It is definitely an issue within ubo, I will add a link to the issue there when I create it.
Edit:
It seems to be caused by the "AdGuard Tracking Protection" filter list within ubo.
Edit: issues:
ubo filters: https://github.com/uBlockOrigin/uAssets/issues/21841
AdguardFilters: https://github.com/AdguardTeam/AdguardFilters/issues/170172
Edit:
It was fixed a few minutes ago, the changes should percolate through to ubo soon™. Thx Yuki2718.

you are viewing a single comment's thread
view the rest of the comments
[-] Redjard@lemmy.dbzer0.com 1 points 2 years ago

Actually it happens on the forked profile too now, restarting ff did not clear the cache there and it only occurs on newly opened pages now, so what I assume happened was I initially tested while ubo was not yet updated, since the laptop has been sleeping for a while. The browser generated a bunch of cache entries for my test pages and those continued working when ff updated ubo. Clearing the cache now has it break on all pages and fix itself when ubo is disabled like on the other device.
Therefore this seems like a clear ubo issue, independent of platform and other factors. All 3 affected profiles have similar ubo config, so I'll investigate that now. However it is not a firefox issue, I will move the issue elsewhere.

this post was submitted on 08 Jan 2024
31 points (97.0% liked)

Firefox

20480 readers
119 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago
MODERATORS
k_o_t@lemmy.ml
golden_zealot@lemmy.ml