Renato Alves

@srtfisher I'm very interested in this issue but it is not clear to me what do you mean by "native support". Could you outline some of the goals you have...

@theMikeD Any update?

The current solution, workaround, is to enable the `Cache-Control: no-store` header **before** activating the Login Nonce feature. So that the login page is not "cached"/snapshotted by the browser.

> When a browser is closed the bfcache is cleared, so the only people who would be getting this bug are people who are attempting to login during the same...

Also, one doesn't need to be attempting to login during the same session as the deploy. They only need to have the login page bfcached. See the steps to reproduce...

I'm reopening this issue since the lastest fix doesn't address the actual issue. > Google are already looking at ways to ignore this header for bfcache Once this is fixed...

I thought of that at first, but see this issue: https://github.com/alleyinteractive/elasticsearch-extensions/issues/52 > I don't think this is something that ES Extensions can (or should) address, mainly because this plugin doesn't...

The other use case would be too, since it was related to a search page only. My main point here is that up until now, we haven't bundled client-side js,...

Somewhat related to this convo. What's the alternative workflow today to check text domains in js/ts files (e.g: blocks/slotfills, etc)? @jrfnl mentioned [here](https://github.com/WordPress/WordPress-Coding-Standards/issues/1641#issuecomment-607347670) to use eslint. But I wonder if...

I guess https://www.npmjs.com/package/@wordpress/eslint-plugin is the way.