Bug found , adguard wont blocking when disabled and r enabled
- Thread starter demoneye
- Start date
chrome 34 on windows 8.1 (update 1 installed)
Just checked this...
1. I can reproduce this multiple times
2. I can fix it without closing the browser multiple times
If you disable adguard and the refresh a page so that you have ads on a site (i used gizmodo there are ads at the bottom) then re-enable adguard and press refresh your right there is no blocking but if you disable adguard again, re-enable it and count to five then refresh the browser, it works fine.
I guess it just needs a little time to warm up.
1. I can reproduce this multiple times
2. I can fix it without closing the browser multiple times
If you disable adguard and the refresh a page so that you have ads on a site (i used gizmodo there are ads at the bottom) then re-enable adguard and press refresh your right there is no blocking but if you disable adguard again, re-enable it and count to five then refresh the browser, it works fine.
I guess it just needs a little time to warm up.
welp ... it doesnt need to be that way ... seems to me as a bug and should be fixed
10x for the solution anyway
While i can understand you want things to be instant you have to remember that adguard is injecting code into chrome and the site that is loaded at the time which of cause can take time specially if you have multiple tabs open. (im guessing more tabs could = more time but iv not tested this).
adguard describe its self as preventing before the ads traffic even come to the pc / browser ... so what the heck ? ... your explanation may fit the adguard extension not the program.
Sorry to say but you dont know what you are on about, when you disable adguard the code injection stops and is removed from the browser it does not stay there just "disabled" so when you re-enable it it needs to be re-injected into the browser from the start again.
So, adguard enabled is doing what its ment to do and stopping ads from reaching the browser, you disabling it and then being inpatient is your fault.
So, adguard enabled is doing what its ment to do and stopping ads from reaching the browser, you disabling it and then being inpatient is your fault.
How is Adguard better than all other ad blockers?
Adguard was developed using sophisticated heuristic algorithms and a wide range of filters that work perfectly in removing ads and popups. Once installed, Adguard silently works in the background and automatically protects you from ads and malicious websites. Though ad-blocking plugins are able to hide a part of advertisements, Adguards removes it completely, saving both Internet traffic and nerves. We created this program around three years ago and have been improving it ever since
How can it protect you if you disabled it? It can not.
You can not say its not working when you have admitted to disabling the product and then are being impatient when you re-enable it. i have explained to you whats happening but you clearly are not listening so im not going to bother anymroe.
i didnt want to use this line but since you dont get it and make other believe u correct i will , they doing what i claim with ad muncher and u will see it works perfect when switching between on/off protection.
Hi all!
I'll try to describe how Adguard work and why this issue is "by design".
When Adguard's protection is enabled we intercept all new connections and filter their traffic.
When you disable Adguard and refresh the web page - new connections are created (we have not intercepted them).
These connections are alive for some time and re-used when you refresh the page again.
The only way for us to fix this issue - is to forcibly close all connections which we have not intercepted yet.
We could do it but personally I don't think that closing connections is a good decision.
I'll try to describe how Adguard work and why this issue is "by design".
When Adguard's protection is enabled we intercept all new connections and filter their traffic.
When you disable Adguard and refresh the web page - new connections are created (we have not intercepted them).
These connections are alive for some time and re-used when you refresh the page again.
The only way for us to fix this issue - is to forcibly close all connections which we have not intercepted yet.
We could do it but personally I don't think that closing connections is a good decision.