I'm using Advanced Conditions to trigger specific actions on different websites in Chrome, but it is not reliable. It seems that BTT only checks the active_website_url whenever Chrome switches to the foreground, but not while it remains the foreground app. Is the the case, @Andreas_Hegenberg?
Screen recording demo: https://youtu.be/ILIuzwF5fJE
Here are my two separate triggers using Advance Conditions:
It sounds like the same issue @Maxime_Bonzi reported here. My triggers/actions work correctly if I switch to another app and then back to Chrome before triggering.
Any ideas? Thanks!
@Andreas_Hegenberg is there a way to force BTT to constantly check the active_website_url? (Updated screen recording: https://youtu.be/ILIuzwF5fJE)
Currently BTT seems to only check it when Chrome switches to the foreground.
For example, to fix a different check interval issue you told me to run this terminal command: defaults write com.hegenberg.BetterTouchTool BTTMouseCheckInterval 0.1.
Is there a similar way to fix the check active_website_url behavior?
I think not yet, but I‘ll add one
1 Like
Thanks, Andreas! 
I don't know if that's the problem or not. Why would having many Chrome tabs open cause BTT's active_website_url condition to fail?
it should have the url of the last focused tab regardless of how many
Makes sense, thanks. So maybe the issue is related to the check interval/frequency issue for the active_website_url behavior condition? I will test as soon as you add a setting for that. Thanks again.
in general BTT relies on a notification from the browser as to when the url changes, but chrome has caused issues in the past here.
I‘m adding a generic way to actively poll CAG properties, it should solve the issue.
(Personally I have migrated from Chrome to Safari, and it has been great - battery life has been so much better since)
1 Like
Excellent, thank you, Andreas! I look forward to testing that with Chrome whenever you can release a BTT update.
As for switching from Chrome to Safari, I will consider it, especially now that Google is forcing the discontinuation of the Manifest V2 framework for extensions.
As you promised, this behaves perfectly in Safari and BTT reads the active_website_url correctly. 
However, I'm stuck using Chrome for now and the active_website_url
BTT condition is still unreliable when I have many tabs open.
Do you know if there are any Chrome flags or OS settings I could change to make this more reliable until you're able to add "a generic way to actively poll CAG properties"? Thanks for all the help!
I’ll be back next week, then I’ll check! I don’t know whether there are any flags that could improve this ;-(
1 Like
Thanks, @Andreas_Hegenberg and enjoy your week away!
@Andreas_Hegenberg any chance this is available in an alpha release? I currently have to alt+tab away from Chrome and then back for BBT to read the active URL reliably. Thanks. 
sorry not yet! I have tried to reproduce the issue in order to be able to test the solution, but in my case it seems to work fine with chrome. Is it maybe some extension that is interfering?
