Failed to implement CSP Policy's for styles with CSP_NONCE token about angular

[JoostK]

This is working as expected; a nonce must be available synchronously during startup.

What's the reasoning for fetching a nonce via the server anyway? Why not generate it locally in the client? That can't normally be done for scripts (as it's a catch 22) but if you have the ability to execute code anyway, then I don't see why you'd need a server to generate a nonce...

[Peter-Zakharevich]

This is working as expected; a nonce must be available synchronously during startup.

What's the reasoning for fetching a nonce via the server anyway? Why not generate it locally in the client? That can't normally be done for scripts (as it's a catch 22) but if you have the ability to execute code anyway, then I don't see why you'd need a server to generate a nonce...

The reason why we're fetching a nonce it's because API side have a control over CSP policies (e.g. alowed chases, nonces e.t.c), Client side receive CSP policies via HTTP headers.
Are you suggesting to implement CSP policies for the styles on the Client side via meta tag ?
In that case, can we use injection of csp_nonce token for meta tag or we have to write some custom logic to populate csp policies there?