dieterdreist left a comment (openstreetmap/openstreetmap-website#6584)
not directly, but it could indirectly prevent the page from qualifying for the
back/forward cache (bfcache) — and bfcache is what restores filled form fields
when you hit Back.
Browsers treat some caching headers as “activity” that makes a page unsafe to
store in memory.
Example
cache-control: no-store → bfcache disabled
cache-control: no-cache → often disables bfcache
cache-control: must-revalidate + max-age=0 → can disable bfcache depending on
browser
This does not prevent form saving directly — but it prevents the entire page
state from being preserved. When the browser cannot put the page in bfcache, it
must reload the document, so no form values survive.
this is a shortened version of an ai reply.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6584#issuecomment-3607706111
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/6584/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
