-
Improvement
-
Resolution: Unresolved
-
None
-
None
-
High
-
Improvement: Replace the browserless headless chrome integration with a native image in the visualbrowser container
-
Emptyshow more show less
Problem
The visualbrowser container is built on a browserless https://www.browserless.io/ . That is problematic since browserless consumes all JS-Errors occuring in the Browser so we cannot see them via the headless protocol. Also browserless unnneccessarily consumes additional RAM
Solution
- Replace Browserless with a native headless chrome or chromium image
- Implement own browser start/shutdown code, may keep one instance always running for responsiveness (must be discussed)