Artur

The problem is https://github.com/vaadin/flow-hilla-common/blob/04f7eea1a5f243078a1596d767d465716d862b95/frontend/packages/common-frontend/src/ConnectionState.ts#L129 and that `navigator.online` is `false` for a mac when the network is disconnected, even if it can connect to the current url. If you change that...

At least when you do not have `@PWA` so no offline page, it should skip the whole logic

You can work around this by adding ``` (window.Vaadin as any).connectionState.connectionState='connected'; ``` to e.g. the end of index.ts

Is that 23.3 + Vite or something else?

For me it works also in Vaadin 23.2.11 the same way. One potential workaround to the workaround would be to add ``` import '@vaadin/common-frontend/ConnectionIndicator.js' ``` to the beginning of index.ts....

ah but you are talking about a typescript error `Property 'Vaadin' does not exist on type 'Window & typeof globalThis'` use `(window as any).Vaadin` instead of `(window.Vaadin as any)`

> My 5 cents is that we should not change current behavior, but introduce API to configure it work differently when needed. What would be the case when you want...

There are no thought-out, ready solutions. If we have a service worker, can we e.g. know from that one if it reached the server for index.html or not? If we...

This also happens seemingly randomly when running `vitest watch` and then you need to restart the process

The hacky workaround here for debugging is to go and edit `node_modules/vitest/dist/vendor/index.cAUulNDf.js` and change the default birpc timeout to something larger, e.g. ``` const DEFAULT_TIMEOUT = 6e7; ```