Local Storage Policy Change in Safari 16.1+

Hi,

To the best of anyone's knowledge, has there been any word from Apple on changes to Local Storage policies in Safari 16.1 and beyond?

Starting around October 24th we began to see users of one of our applications fail to make a bridge from one application to another.

In short, we use an iframe to set information in local storage on a subdomain.

When we move the user to that subdomain and go to retrieve local storage it is no longer there.

In all previous versions of Safari, current and past versions of Chrome and Firefox the solution works.

We can only ascertain that this is a bug or a bug that appears to look like a security feature.

Related posts we have reviewed have mentioned Local Storage size limits, etc. We see this issue at any size.

We need some direction from the developer community on what this is and where it may go.

Do you have any information?

I am facing the same issue with session Storage..

I have the same issue!

Adding a session Storage entry using for example postMessage to an iframe for a "domain.com" from "app.domain.com" will not work. This works in chrome like always did!

So this is breaking some code... :(

Local Storage Policy Change in Safari 16.1+
 
 
Q