@Fox Good link there. Unfortunately, that code, executed right before a Page Load, doesn't mute Ajax-called elements like audio players or video ads. Too bad they didn't allow for a setting within the Browser or within a Chromium call itself. Thanks for the tip on Google Translate - works great!
Seems to be a bug, if you have tunneling enabled it leaks your ip and if you disable tunneling you can't continue to click to next page on some urls, seems to be a bug.
If you are a coder. U will understand that. Firefox allow user raise . But Chrome cant. Google limit 6 on Chrome. If u can raise it in "Brower Auto Studio" It will make work faster
