Hector Morales

cc: @EmLauber can we track this sample request internally please? Thanks!

@janandreschweiger thanks for updating us, I'll start looking into factoring in ID token expiration into the cache logic.

@anvipul popup APIs are not supported with those security policies. Isolating the pop-ups makes it so MSAL cannot access the popup once it's opened. Please use acquireToken/loginRedirect or remove those...

@anvipul I was able to repro this behavior. As it stands now it seems `restrict-properties` is an experimental Chrome feature in trial that may or may not be kept. @EmLauber...

To add some context, supporting scenarios with `restrict-properties` would require MSAL to migrate from polling the popup's window.location.hash directly to a pub/sub approach in which MSAL posts a message to...

@waxisien could you provide a screenshot showing where you want the popup to appear so we can better understand the request? Thanks.

@sameerag may have more context here. We generally try to stay away from static variables, but we do leverage a sort of request cache in msal-browser that prevents multiple identical...

@grosch-intl thanks for the feature request. We'll look into it but as a general rule we're not doing API breaking changes for v3. We're limiting updates to default behavior breaking...

@kiranchandran @mkArtakMSFT It seems like MSAL.js is working as designed. The iframe warning is not a breaking error, it is expected for some cases and handled by MSAL by throwing...

@kiranchandran @mkArtakMSFT MSAL Browser does have a configuration option called [`CacheLookupPolicy`](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/6ea22f4c9625c22aaa8815fed829ded255423ceb/lib/msal-browser/docs/token-lifetimes.md#cache-lookup-policy) that can be configured per-request. Using `CacheLookupPolicy.AccessTokenAndRefreshToken` will return the `InteractionRequired` error before attempting iframe renewal. Example: ```typescript var...