Firefox

17955 readers

625 users here now

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

founded 4 years ago

MODERATORS

[fixed, caused by filter list within uBlock Origin] What happened to the back history caching in 120 or 121? (lemmy.dbzer0.com)

submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

10 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

[–] feef 1 points 10 months ago (2 children)

Did you find the cause?

[–] [email protected] 1 points 10 months ago

Yes, I just updated the post, you can see the process in my various comments.
It seems to be caused by uBlock origin, though I haven't yet investigated deeper. It might be the combination of the firefox version and the ubo version, and it may be dependent on a specific setting within ubo, I don't know yet.

[–] [email protected] 1 points 10 months ago

I found it is fixed when I disable the "AdGuard Tracking Protection" list. It can also be "fixed" by setting cacheControlForFirefox1376932 to unset or no-cache in advanced settings, but I don't think that's a good idea to do.