Atle Sjønøst

Angular-cli abstracts away webpack, and give no easy options for customizing the webpack config used internally. It still works with this warning though, it just signals that it might not...

eagerly awaiting this now that the blocker is resolved, will it also fix the tooltip positioning in zoneless?

I can easily reproduce on my win 11 laptop, but not with angular build or serve, or crystal based jest or lint... But I run into this with commands running...

Still getting this error with 18.2.4 and the updated pty version for windows

I also observe that http3 is used, which multiplexes requests and run on udp. Is buffering proxies common for this transport?

I set this in initializeFirestore, which is only called once at startup. Can this setting be changed other than in initializeFirestore? I just disable experimentalAutoDetectLongPolling for now, assuming buffering proxies...

It was what you suggested above; to enable/disable it together with enabling/disabling network. But I don't really want such a solution, I would rather that your experimentalAutoDetectLongPolling algorithm supports my...

I never said LongPolling is enabled while network is disabled... I said that when disabling/enabling network the LongPolling is often enabled un-necessary, as it seems to interfere with your auto-detect...

I enable/disable on visibilitychange... you can call function below in a web app and switch tabs or hide/show window... Almost immediately you can see the data traffic switching to long...

tested with beta 6 and angular, and cli/build doesn't report any warnings now:-)