dynamic choice of browser context #107
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
P2
Although
chromium-headless
andchromium-heaful
are registered into BrowserContextFactory,we can only choose one for all tasks(workflows) because we create the type by reading the config in env.
skyvern/skyvern/webeye/browser_factory.py
Line 86 in d273510
Is it necessary to offer a dynamic option? maybe at the task(workflow) level? Like task(workflow) A could choose headless and task(workflow) B could choose headful?
Sure, the BROWSER_TYPE in the env config could be the default choice if not browser type is specified by the task(workflow).
The text was updated successfully, but these errors were encountered: