I found a funny bug (or bad behaviour at least)
The value of BTT_PRESET_PATH is sometimes set to an unexpected value.
This is with 3.328
To reproduce this,
- set your preset to not default and generate a trigger (I associate it to the opening of a html page)
this html opened as expected -> correct BTT_PRESET_PATH
- change your preset to default
- edit the previous trigger and add a second web view
This second webview does not open. The reason is that the BTT_PRESET_PATH for this second action is set to the default preset and not the one associated to the trigger...
The workaround is simple obviously.