Brent Gervais

hmm, unfortunately confirming that this behaviour occurs on a freshly opened browser session with a freshly loaded page aswell. So... my speculations on potential cause are somewhat dismissed.

This issue occurred again on 2023-12-12 (Firefox) The method thought to be able to reproduce it is not reliable. Will continue searching for a reliable method to reproduce...

Confirming again this behaviour just occurred. Is there anything I can capture that would be helpful in diagnosing or investigating this behaviour? Any ideas?

Behaviour screencast and console log provided internally to engineering - reason: potentially sensitive. Will update here when more is discovered.

great! A new demo is exciting. Might I recommend removing references to the demo until it is ready?